Dynamic Payment Optimization Apparatuses, Methods and Systems

ABSTRACT

The DYNAMIC PAYMENT OPTIMIZATION APPARATUSES, METHODS AND SYSTEMS (“DPO”) transform requests for on-demand and flexible monetization and related services via DPO components into currency transfers, purchase receipt notifications, social networking communications and transaction analytics reports. In some embodiments, the DPO obtains a user product purchase request for a user engaged in an online experience at a point of sale device. The DPO parses the user product purchase request, and thereby identifies at least one attribute of at least one of: the user; the online experience; and the point of sale device. The DPO customizes one or more properties of a user interface for initiating a purchase transaction related to the user product purchase request, according to the identified at least one attribute of the user, the online experience or the point of sale device; and providing the customized user interface.

PRIORITY CLAIM

This application claims priority under 35 USC §119 to: U.S. provisionalpatent application Ser. No. 61/455,378 filed Oct. 20, 2010, entitled“SOFTWARE AND METHOD FOR CONFIGURATION OF VIRTUAL CURRENCIES AND VIRTUALCURRENCY PRICING FOR GLOBAL ONLINE MERCHANTS,” attorney docket no.PS-99007PRV|20270-169PV; U.S. provisional patent application Ser. No.61/455,379 filed Oct. 20, 2010, entitled “TRACKING AND DISPLAY METHODAND SOFTWARE FOR REPRESENTATION OF PAYMENT PROCESSING AND VOLUMES BYGEOGRAPHIC REGION,” attorney docket no. PS-99008PRV|20270-170PV; U.S.provisional patent application Ser. No. 61/455,383 filed Oct. 20, 2010,entitled “SYSTEM AND METHOD FOR PERSON-2-PERSON (P2P) ECOMMERCEAFFILIATE MARKETING UTILIZING SOCIAL NETWORKS,” attorney docket no.PS-99009PRV|20270-171PV; United States provisional patent applicationSer. No. 61/455,454 filed Oct. 21, 2010, entitled “DYNAMIC OPTIMIZATIONAND DISPLAY OF PAYMENT METHOD FOR GLOBAL, ON-LINE COMMERCE WEBSITES,”attorney docket no. PS-99011PRV|20270-173PV; U.S. provisional patentapplication Ser. No. 61/456,118 filed Nov. 2, 2010, entitled “SOFTWARE,METHOD AND SYSTEM FOR MONETIZATION AS A SERVICE,” attorney docket no.PS-99013PRV|20270-174PV; and U.S. provisional patent application Ser.No. 61/506,425 filed Jul. 11, 2011, entitled “HOSTED ORDER PAGE PAYMENTTYPE SELECTION,” attorney docket no. 15US01|20270-200PV. The entirecontents of the aforementioned applications are expressly incorporatedby reference herein.

This document describes inventive aspects that include various novelinnovations (hereinafter “disclosure”) and contains material that issubject to copyright, mask work, and/or other intellectual propertyprotection. The respective owners of such intellectual property have noobjection to the facsimile reproduction of the disclosure by anyone asit appears in published Patent Office file/records, but otherwisereserve all rights.

FIELD

The present innovations generally address apparatuses, methods, andsystems for electronic commerce, and more particularly, include DYNAMICPAYMENT OPTIMIZATION APPARATUSES, METHODS AND SYSTEMS (“DPO”).

BACKGROUND

Consumers engaging in transactions typically select a product from astore shelf or website, and then check them out at a checkout counter orwebpage. Product information is typically selected from a webpagecatalog or entered into a point-of-sale terminal device. The consumerutilizes a payment option, such as cash, check, credit card, or debitcard, to pay for the transaction. Once payment is made, thepoint-of-sale terminal device memorializes the transaction in themerchant's computer system, and a receipt is generated indicatingsatisfactory consummation of the transaction.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying appendices and/or drawings illustrate variousnon-limiting, example, inventive aspects in accordance with the presentdisclosure:

FIG. 1 shows a block diagram illustrating example aspects of flexiblemonetization services in some embodiments of the DPO;

FIG. 2 shows a block diagram illustrating an example DPO componentconfiguration in some embodiments of the DPO;

FIGS. 3A-E show user interface diagrams illustrating example features ofstandalone app and web interfaces for a virtual wallet application insome embodiments of the DPO;

FIGS. 4A-E show user interface diagrams illustrating example features ofa flexible monetization service web browser interface in someembodiments of the DPO;

FIGS. 5A-D show user interface diagrams illustrating example features ofdynamic payment optimization and virtual currency configuration, as partof providing flexible monetization services, in some embodiments of theDPO;

FIGS. 6A-D show user interface diagrams illustrating example, featuresof geographic transaction volume analytics in some embodiments of theDPO;

FIG. 7A-C show block and data flow diagrams illustrating an examplepurchase catalog browsing procedure in some embodiments of the DPO;

FIG. 8 shows a logic flow diagram illustrating example aspects ofpurchase catalog browsing in some embodiments of the DPO, e.g., aPurchase Catalog Browsing (“PCB”) component 800;

FIG. 9 shows a data flow diagram illustrating an example user purchasecheckout procedure in some embodiments of the DPO;

FIG. 10 shows a logic flow diagram illustrating example aspects of userpurchase checkout in some embodiments of the DPO, e.g., a User PurchaseCheckout (“UPC”) component 1000;

FIGS. 11A-B show data flow diagrams illustrating an example flexiblemonetization service procedure in some embodiments of the DPO;

FIGS. 12A-B shows logic flow diagrams illustrating example aspects offlexible monetization service in some embodiments of the DPO, e.g., aFlexible Monetization Service (“FMS”) component 1200;

FIGS. 13A-F show block and logic flow diagrams illustrating exampleaspects of virtual currency configuration in some embodiments of theDPO, e.g., a Virtual Currency Configuration (“VCC”) component 1300;

FIG. 14 shows a logic flow diagram illustrating example aspects ofdynamic payment optimization in some embodiments of the DPO, e.g., aDynamic Payment Optimization (“DPO”) component 1400;

FIGS. 15A-B show data flow diagrams illustrating an example purchasetransaction authorization procedure in some embodiments of the DPO;

FIGS. 16A-B show logic flow diagrams illustrating example aspects ofpurchase transaction authorization in some embodiments of the DPO, e.g.,a Purchase Transaction Authorization (“PTA”) component 1600;

FIGS. 17A-D show block and data flow diagrams illustrating an exampleperson-2-person social network marketing procedure in some embodimentsof a the DPO;

FIGS. 18A-B shows logic flow diagrams illustrating example aspects ofperson-2-person social network marketing in some embodiments of the DPO,e.g., a Person-2-Person (P2P) Social Network Marketing (“P2P-SNM”)component 1800;

FIGS. 19A-B show data flow diagrams illustrating an example purchasetransaction clearance procedure in some embodiments of the DPO;

FIGS. 20A-B show logic flow diagrams illustrating example aspects ofpurchase transaction clearance in some embodiments of the DPO, e.g., aPurchase Transaction Clearance (“PTC”) component 2000;

FIG. 21 shows a data flow diagram illustrating an example geographictransaction volume analytics procedure in some embodiments of the DPO;

FIG. 22 shows a logic flow diagram illustrating example aspects ofgeographic transaction volume analytics in some embodiments of the DPO,e.g., a Geographic Transaction Volume Analytics (“GTVA”) component 2200;and

FIG. 23 shows a block diagram illustrating embodiments of a DPOcontroller.

The leading number of each reference number within the drawingsindicates the figure in which that reference number is introduced and/ordetailed. As such, a detailed discussion of reference number 101 wouldbe found and/or introduced in FIG. 1. Reference number 201 is introducedin FIG. 2, etc.

DETAILED DESCRIPTION Dynamic Payment Optimization (DPO)

The DYNAMIC PAYMENT OPTIMIZATION APPARATUSES, METHODS AND SYSTEMS(hereinafter “DPO”) transform requests for on-demand and flexiblemonetization and related services, via DPO components, into currencytransfers, purchase receipt notifications, social networkingcommunications and transaction analytics reports.

Business-to-consumer (B2C) companies may build their customer billingoperations through a mix of in-house software development, third-partypayment processor integrations and various third-party software productsfor subscription, fraud management and commerce systems depending on thebusiness models they adopt. As the cost for customer acquisition andretention increases, more and more sophisticated monetization models maybe required to drive higher conversion rates and Average Revenue PerUser (ARPUs) from paying users.

In some embodiments, the DPO implements a flexible monetization platformbased on a completely new way of thinking about how to monetizedifferent types of users at various price points and at different lifecycle stages of customers' engagement with the content offered. It callsfor a 360-degree view of a customer who is looking to access and consumecontent across devices, platforms and networks. For example, when a lotof AAA content is available for free, merely setting a $14.99 monthlysubscription price point and up-sell buckets may limit revenuegeneration capabilities. Consumers may want to pay at their own pace andat the price point they can afford. Thus, in some embodiments, the DPOenables a disruptive business model of microtransactions, which unlocksa massive consumer base that could become paying customers. Moreover theoperational costs, and overheads with operating customer billingoperations inhouse, or through a mix of in-house and third partysolutions may become unnecessarily expensive for the B2C companies sincetheir payment volumes do not justify the investment needed. Furthermore,billing teams may not be able to keep up with the need for updates,improvements, or inclusion of new technologies or new payment methods.

FIG. 1 shows a block diagram illustrating example aspects of flexiblemonetization services in some embodiments of the DPO. In someembodiments, the DPO may provide merchants and/or users with a varietyof features to facilitate an expedited shopping experience. For example,a user, e.g., 101, may desire a secure, fast, and enjoyable shoppingexperience in, either at a physical brick-and-mortar store 102 a, or anonline website (e.g., a gaming site, a gaming application, an eCommercewebsite, etc.) 102 b. A merchant, e.g., 102, may desire to provideservices and a shopping experience to match the user's desires, e.g., tomaximize customer retention and/or ensure that the customers completetheir purchase transactions when they are at a point-of-sale, e.g., 112.In some embodiments, a payment network, e.g., a credit card company, maybe able to provide the merchants and/or user with infrastructure tofacilitate such provision of shopping experiences, so that the merchantneed not recreate the infrastructure for their business, e.g., 113. Forexample, the DPO may provide a stack of application services, from whichthe merchant can select according to the merchant's needs. In someembodiments, the DPO may provide applications that can be customized bythe merchants to provide the appearance that the provided service isseamlessly integrated with the merchant's systems, while outsourcing theprocessing associated with those services provided by the DPO. In someembodiments, the DPO may provide application services that canautomatically customize themselves according to the needs of the user,e.g., as adjudged by transaction analytics and/or the like user behavioranalysis, e.g., 114.

FIG. 2 shows a block diagram illustrating an example DPO componentconfiguration in some embodiments of the DPO. In some embodiments, theDPO may enable online commerce sites to utilize a third party solutionas a service to manage, operate and maintain the various components usedin conducting and facilitating online transactions. In some embodiments,the DPO may provide merchants with a variety of application services toenhance the consumer shopping experience during purchase product catalogbrowsing, e.g., 201, user purchase checkout, e.g., 202, purchasetransaction authorization, e.g., 203, and/or purchase transactionclearance, e.g., 204. In some embodiments, the merchant may makerequests for such services to the DPO via a flexible monetizationservices interface, e.g., 205. For example, the DPO may provide anapplication programming interface (API) for the merchant to request suchservices.

In some embodiments, a service provided by the DPO may include, e.g.,206 a, the ability to select from a plurality of payment serviceproviders (PSP) for routing the transaction, but from the same userinterface, see e.g., FIGS. 4A-E. In some embodiments, the DPO may offera large variety of payment methods to users, and determine what methodsto offer to what segment of the user base in specific countries tomaximize conversion. In some embodiments, the DPO may manage a vastamount of technical integrations with PSPs, but obfuscate thedifferences by presenting the merchant with a single integration. EachPSP may have its own interfaces and APIs and so the complexity inproviding a unified customer experience may be large. In someembodiments, the DPO may handle this complexity to present a unifiedconsistent experience to consumers making purchasing transactions. Thisunified integration may take the form of either API integration in someembodiments, or the use of widgets or front end pages that manage thepayments on behalf of the merchant in other embodiments. In order tocreate the single integration touch point for the merchant, in someembodiments, the DPO may have a translation module that repurposes allthe various integration, settlement, and use of third party PSPs into acommon infrastructure. Because of this unified User Interface andunified integration APIs, the the DPO may allow the continued additionor updating of payment customers without requiring that the merchantsmake updates or changes to their integration or billing systems.

In some embodiments, a service provided by the DPO may include, e.g.,206 b, risk management services for the user and/or merchant, includingfraud detection and prevention, identity theft, and/or the like. Forexample, the DPO may manage risk by using a comprehensive fraud engineto monitor and prevent and minimize the number of fraudulenttransactions that occur. The Fraud Engine may gather information frommultiple sources such as third party fraud services such as negativefile databases, AVS matching services, device fingerprinting servicesand/or the like. The Fraud Engine may combine these various data pointsas well as analyzes historical data to create heuristics and rules toprevent fraudulent transactions from occurring. The DPO, in someembodiments, may also provide a number of on-demand reports that helpmerchants gain insight into the incidence of fraud on their site andtune and configure their detection rules to better prevent fraud whilemaintaining a positive customer experience.

In some embodiments, a service provided by the DPO may include, e.g.,206 c, micro-payment and subscription services. In some embodiments, theDPO may include an electronic wallet that maintains stored valuebalances for user accounts either in the form of real world balances orvirtual currency balances. These balances may be broken down and trackedaccording to the method of payment made to create the balance such thatthe merchants can gain visibility into the actual cost basis for anyuser's balance. The DPO may further include subscription, and recurringbilling engines and related features such as automatic entitlementdelivery, overdue bill collection and event notifications. As anotherexample, the DPO may include tracking of account balances, spendtracking, billing and/or product subscriptions, product offers and/orrecommendations, event notifications, and/or the like.

In some embodiments, a service provided by the DPO may include in-appoptimization, e.g., 206 d. In order to collect payments, the front enduser experience around the presentation of purchasing options may beoptimized by the DPO for the individual user in order to maximize thelikelihood of a user completing a transaction. One such method that maybe used by the DPO in some embodiments is lightbox (pop-up) front end UIthat is embedded on the merchants site through the use of for example,javascript. Users who click the Buy button may experience a pop-upwindow that is seamlessly integrated into the merchant site, with a lookand feel that is customized to the merchant site. This lightboxexperience may allow the user to stay within the payment windowexperience and the transaction may be completed within this sameexperience and not require that the user be redirected to an alternatewebsite to transact a payment. In some embodiments, the Lightbox mayhave a dynamic user interface that reorders the payment methods in theorder that is most likely to have a user complete a transaction based onthe users demographic information as well as historic data around userspurchasing activity and payment method preferences. For example, usersin country A may see payment option X and Y listed first, because thosemethods convert highly in country A, whereas a user in Country B may seepayment options Z listed first because that method converts highly incountry B. In general, the DPO may provide features to modify thefront-end user experience of a user purchasing a product to maximize thelikelihood of the user completing the purchase and/or returning to themerchant's site for additional purchases. For example, the DPO may allowfor configuration of the user interface according to the user'sdemographics, behavior, location, language, payment preferences (eitherspecific to the user, or generally for the user's demographic), and/orthe like.

In some embodiments, the DPO may provide storefronts and/or marketplacesfor users to browse products for purchase. Before a user can make apayment, they need to see which items they desire to purchase. The DPOmay include a presentation layer and front end user interface in theform of a storefronts (app stores/marketplace) where items are presentedto users. The DPO may further provide the necessary backendinfrastructure to enable storefronts to function such as inventorymanagement modules, catalog and offer management modules, merchandizingmodules, coupon code and discount promotion modules, inclusion ofvirtual currency wallet across games, one-click purchases,recommendation engine, search engine. In general, DPO may provideback-end services for the merchants, including inventory management,product search, advertisement placement, offer managements, consumerpurchase incentives such as rewards or discounts, and/or the like.

In some embodiments, the DPO may provide analytics for the merchantbased on card transaction data obtained from users purchasing productsfrom the merchant, e.g., 206 f. In some embodiments, the DPO may alsoallow developers to develop third-party apps that may be provided by theDPO to merchants via an application service store for the merchants. Forexample, the DPO may provide a Developer Console that gives clients theinformation they need in a unified fashion for all aspects of the MaaSstack. Reports and data include products, pricing or revenue by paymentmethod and/or country, spending patterns, free-to-paid conversion andARPU metrics.

In some embodiments, the DPO may provide customer support services, suchas on-demand live video/text chat, and/or the like services, for theusers, e.g., 206 g. For example, in some embodiments, the DPO mayfacilitate a Developer Console that provides role based permissions toallow users of different levels to access different parts of theplatform. One such level may be a customer support representative whocan gain access to user transaction data to assist them with any issues,but would not gain access to other information such as revenue reports.The customer support tools may include ability for CS reps to issuerefunds, look up pending transactions as well as whitelist or black listusers.

FIGS. 3A-E show user interface diagrams illustrating example features ofstandalone app and web interfaces for a virtual wallet application insome embodiments of the DPO. With reference to FIG. 3A, in someembodiments, a virtual wallet mobile app, e.g., 311, executing on adevice, e.g., 300, of a user may include an app interface providingvarious features for the user. For example, the device may include acamera via which the app may acquire image frames, video data, livevideo, and/or the like, e.g., 316. The app may be configured to analyzethe incoming data, and search, e.g., 312, for a product identifier,e.g., 314, such as barcodes, QR codes and/or the like.

In some embodiments, the app may be configured to automatically detect,e.g., 312, the presence of a product identifier within an image or videoframe grabbed by the device (e.g., via a webcam, in-built camera, etc.).For example, the app may provide a “hands-free” mode of operationwherein the user may move the device to bring product identifiers withinthe field of view of the image/video capture mechanism of the device,and the app may perform image/video processing operations toautomatically detect the product identifier within the field of view. Insome embodiments, the app may overlay cross-hairs, target box, and/orlike alignment reference markers, e.g., 315, so that a user may alignthe product identifier using the reference markers to facilitate productidentifier recognition and interpretation.

In some embodiments, the detection of a product identifier may triggervarious operations to provide products, services, information, etc. forthe user. For example, the app may be configured to detect and capture aQR code having embedded merchant and/or product information, and utilizethe information extracted from the QR code to process a transaction forpurchasing a product from a merchant. As other examples, the app may beconfigured to provide information on related products, quotes, pricinginformation, related offers, (other) merchants related to the productidentifier, rewards/loyalty points associated with purchasing theproduct related to the product identifier, analytics on purchasingbehavior, alerts on spend tracking, and/or the like.

In some embodiments, the app may include user interface elements toallow the user to manually search, e.g., 313, for products (e.g., byname, brand, identifier, etc.). In some embodiments, the app may providethe user with the ability to view prior product identifier captures(see, e.g., 317 a) so that the user may be able to better decide whichproduct identifier the user desires to capture. In some embodiments, theapp may include interface elements to allow the user to switch back andforth between the product identification mode and product offerinterface display screens (see, e.g., 317 b), so that a user mayaccurately study deals available to the user before capturing a productidentifier. In some embodiments, the user may be provided withinformation about products, user settings, merchants, offers, etc. inlist form (see, e.g., 317 c) so that the user may better understand theuser's purchasing options. Various other features may be provided for inthe app (see, e.g., 317 d). In some embodiments, the user may desire tocancel product purchasing; the app may provide the user with a userinterface element (e.g., 318) to cancel the product identifierrecognition procedure and return to the prior interface screen the userwas utilizing.

With reference to FIG. 3B, in some embodiments, the app may include anindication of the location (e.g., name of the merchant store,geographical location, information about the aisle within the merchantstore, etc.) of the user, e.g., 321. The app may provide an indicationof a pay amount due for the purchase of the product, e.g., 322. In someembodiments, the app may provide various options for the user to pay theamount for purchasing the product(s). For example, the app may utilizeGPS coordinates associated with the device to determine the merchantstore within which the user is present, and direct the user to a websiteof the merchant. In some embodiments, the app may be configured to makean application programming interface (“API”) call to participatingmerchants to directly facilitate transaction processing for purchases.In some embodiments, a merchant-branded app may be developed with anin-app purchasing mode, which may directly connect the user into themerchant's transaction processing system. For example, the user maychoose from a number of cards (e.g., credit cards, debit cards, prepaidcards, etc.) from various card providers, e.g., 323 a. In someembodiments, the app may provide the user the option to pay the purchaseamount using funds included in a bank account of the user, e.g., achecking, savings, money market, current account, etc., e.g., 323 b. Insome embodiments, the user may have set default options for which card,bank account, etc. to use for the purchase transactions via the app. Insome embodiments, such setting of default options may allow the user toinitiate the purchase transaction via a single click, tap, swipe, and/orother remedial user input action, e.g., 323 c. In some embodiments, whenthe user utilizes such an option, the app may utilize the defaultsettings of the user to initiate the purchase transaction. In someembodiments, the app may allow the user to utilize other accounts (e.g.,Google™ Checkout, Paypal™ account, etc.) to pay for the purchasetransaction, e.g., 323 d. In some embodiments, the app may allow theuser to utilize rewards points, airline miles, hotel points, electroniccoupons, printed coupons (e.g., by capturing the printed coupons similarto the product identifier) etc., to pay for the purchase transaction,e.g., 323 e. In some embodiments, the app may provide an option toprovide express authorization before initiating the purchasetransaction, e.g., 324. In some embodiments, the app may provide aprogress indicator provide indication on the progress of the transactionafter the user has selected an option to initiate the purchasetransaction, e.g., 325. In some embodiments, the app may provide theuser with historical information on the user's prior purchases via theapp, e.g., 327 a. In some embodiments, the app may provide the user withan option to share information about the purchase (e.g., via email, SMS,wall posting on Facebook®, tweet on Twitter™, etc.) with other usersand/or control information shared with the merchant, acquirer, paymentnetwork etc., to process the purchase transaction, e.g., 327 b. In someembodiments, the app may provide the user an option to display theproduct identification information captured by the client device (e.g.,in order to show a customer service representative at the exit of astore the product information), e.g., 327 c. In some embodiments, theuser, app, device and or purchase processing system may encounter anerror in the processing. In such scenarios, the user may be able to chatwith a customer service representative (e.g., VerifyChat 327 d) toresolve the difficulties in the purchase transaction procedure.

In some embodiments, the user may select to conduct the transactionusing a one-time anonymized credit card number, see e.g., 323 f. Forexample, the app may utilize a pre-designated anonymized set of carddetails (see, e.g., “AnonCard1,” “AnonCard2”). As another example, theapp may generate, e.g., in real-time, a one-time anonymous set of carddetails to securely complete the purchase transaction (e.g., “Anon It1X”). In such embodiments, the app may automatically set the userprofile settings such that the any personal identifying information ofthe user will not be provided to the merchant and/or other entities. Insome embodiments, the user may be required to enter a user name andpassword to enable the anonymization features.

With reference to FIG. 3C, in some embodiments, the user interfaceelements of the app may be advantageously arranged to provide the userthe ability to process a purchase with customized payment parameterswith a minimum number of user inputs applied to the user's device. Forexample, if the user has a QR pay code, e.g., 332, within the viewingangle of a camera included in the user's mobile device, the user mayactivate a user interface element to snap the QR code. In someembodiments, the user may control the field of view of the camera usinga user interface zoom element, e.g., 333. In some embodiments, the userinterface may be designed such that the user may touch an image of a QRcode displayed on the screen to capture the QR code (see e.g., 334). Forexample, the position of the user's touch may be utilized as an input byan image processing module executing on the user's device to process thedisplayed video frame (and/or adjacent video frames), and extract the QRcode from the frame(s) based on the user's input. For example, theuser's touch may provide an approximate center point of the QR code.Using this information, the image processing module may be able tobetter perform an automated QR code image recognition, and accordinglycapture the correct QR code (e.g., if portions of many QR codes aredisplayed within the video frame(s)) selected by the user for captureand processing.

In some embodiments, the app may utilize predetermined default settingsfor a particular merchant, e.g., 331, to process the purchase based onthe QR code (e.g., in response to the user touching an image of a QRcode displayed on the screen of the user device). However, if the userwishes to customize the payment parameters, the user may activate a userinterface element 335 (or e.g., press and continue to hold the image ofthe QR code 332). Upon doing so, the app may provide a pop-up menu,e.g., 337, providing a variety of payment customization choices, such asthose described with reference to FIG. 3B. The user may, e.g., drag theuser's finger to the appropriate settings the user prefers, and releasethe user's finger from the touchscreen of the user's mobile device toselect the setting for payment processing. In alternate embodiments, thepayment settings options, e.g., 337, and QR capture activation button,e.g., 336 may be included in the user interface along with a window forcapturing the QR code via the mobile device's camera. In alternateembodiments, the user's mobile device may generate a hybrid QRcode-payment settings graphic, and the POS terminal (or user's trustedcomputing device) may capture the entire graphic for payment processing.In some embodiments, the app may provide a user interface element 338for the user to minimize the payment options settings user interfaceelements. In some embodiments, the app may provide additional userinterface elements, e.g., 339, to display previous purchases, datashared about those purchases, purchase receipts (e.g., via barcodes) andcustomer support options (e.g., VerifyChat).

With reference to FIG. 3D, in some embodiments, the user may be able toview and/or modify the user profile and/or settings of the user, e.g.,by activating user interface element 322 (of FIG. 3B). For example, theuser may be able to view/modify a user name (e.g., 341 a-b), accountnumber (e.g., 342 a-b), user security access code (e.g., 343 a-b), userpin (e.g., 344 a-b), user address (e.g., 345 a-b), social securitynumber associated with the user (e.g., 346 a-b), current device GPSlocation (e.g., 347 a-b), user account of the merchant in whose storethe user currently is (e.g., 348 a-b), the user's rewards accounts(e.g., 349 a-b), and/or the like. In some embodiments, the user may beable to select which of the data fields and their associated valuesshould be transmitted to facilitate the purchase transaction, thusproviding enhanced data security for the user. For example, in theexample illustration in FIG. 3D, the user has selected the name 341 a,account number 342 a, security code 343 a, merchant account ID 348 a andrewards account ID 349 a as the fields to be sent as part of thenotification to process the purchase transaction. In some embodiments,the user may toggle the fields and/or data values that are sent as partof the notification to process the purchase transactions. In someembodiments, the app may provide multiple screens of data fields and/orassociated values stored for the user to select as part of the purchaseorder transmission. In some embodiments, the app may obtain the GPSlocation of the user. Based on the GPS location of the user, the app maydetermine the context of the user (e.g., whether the user is in a store,doctor's office, hospital, postal service office, etc.). Based on thecontext, the app may present the appropriate fields to the user, fromwhich the user may select fields and/or field values to send as part ofthe purchase order transmission.

For example, a user may go to doctor's office and desire to pay theco-pay for a doctor's appointment. In addition to basic transactionalinformation such as account number and name, the app may provide theuser the ability to select to transfer medical records, healthinformation, which may be provided to the medical provider, insurancecompany, as well as the transaction processor to reconcile paymentsbetween the parties. In some embodiments, the records may be sent in aHealth Insurance Portability and Accountability Act (HIPAA)-compliantdata format and encrypted, and only the recipients who are authorized toview such records may have appropriate decryption keys to decrypt andview the private user information.

With reference to FIG. 3E, in some embodiments, the app executing on theuser's device may provide a “VerifyChat” feature for fraud prevention(e.g., by activating UI element 327 d in FIG. 3B). For example, the DPOmay detect an unusual and/or suspicious transaction. The DPO may utilizethe VerifyChat feature to communicate with the user, and verify theauthenticity of the originator of the purchase transaction. In variousembodiments, the DPO may send electronic mail message, text (SMS)messages, Facebook® messages, Twitter™ tweets, text chat, voice chat,video chat (e.g., Apple FaceTime), and/or the like to communicate withthe user. For example, the DPO may initiate a video challenge for theuser, e.g., 351 a. For example, the user may need to presenthim/her-self via a video chat, e.g., 352 a. In some embodiments, acustomer service representative, e.g., agent 355 a, may manuallydetermine the authenticity of the user using the video of the user. Insome embodiments, the DPO may utilize face, biometric and/or likerecognition (e.g., using pattern classification techniques) to determinethe identity of the user, e.g., 354 a. In some embodiments, the app mayprovide reference marker (e.g., cross-hairs, target box, etc.), e.g.,353 a, so that the user may the video to facilitate the DPO's automatedrecognition of the user. In some embodiments, the user may not haveinitiated the transaction, e.g., the transaction is fraudulent. In suchembodiments, the user may cancel, e.g., 358 a, the challenge. The DPOmay then cancel the transaction, and/or initiate fraud investigationprocedures on behalf of the user. In some embodiments, the app mayprovide additional user interface elements, e.g., to display previoussession 356 a, and provide additional customer support options (e.g.,VerifyChat 357 a).

In some embodiments, the DPO may utilize a text challenge procedure toverify the authenticity of the user, e.g., 351 b. For example, the DPOmay communicate with the user via text chat, SMS messages, electronicmail, Facebook® messages, Twitter™ tweets, and/or the like. The DPO maypose a challenge question, e.g., 352 b, for the user. The app mayprovide a user input interface element(s) (e.g., virtual keyboard 353 b)to answer the challenge question posed by the DPO. In some embodiments,the challenge question may randomly selected by the DPO automatically;in some embodiments, a customer service representative 355 b maymanually communicate with the user. In some embodiments, the user maynot have initiated the transaction, e.g., the transaction is fraudulent.In such embodiments, the user may cancel, e.g., 358 b, the textchallenge. The DPO may then cancel the transaction, and/or initiatefraud investigation procedures on behalf of the user. In someembodiments, the app may provide additional user interface elements,e.g., to display previous session 356 b, and provide additional customersupport options (e.g., VerifyChat 357 b).

FIGS. 4A-E show user interface diagrams illustrating example features ofa flexible monetization service web browser interface in someembodiments of the DPO. As shown in FIG. 4A, in some embodiments, alight box 410 may be instantiated to complete a transaction (e.g.,buying 1000 Gold Coins for $10.00) between a user and a merchant. Thelight box web interface may include various payment options 412 forselection by the user. Non-limiting examples of the payment optionsinclude credit and/or debit cards such as VISA, MASTERCARD, AMERICANEXPRESS and DISCOVER, PAYPAL, bank account and/or personal checkinformation, and/or the like. In some embodiments, the payment optionsthat may be provided may be based on the country where the transactionis conducted. The country option 411 may be pre-selected for the user orthe user may change it. When the “pay with credit card” option isselected, a series of fields 413 may be provided to the user forentering credit card details. Example fields of information required forpurchase with credit card include name on card, address, city,state/region, zip/postal, country, and/or the like. Once all thenecessary information is entered in the provided fields 413, the usermay click on the confirm payment button 414 to authorize payment andcomplete the transaction.

With reference to FIG. 4B, in some embodiments, after the user hasconfirmed payment, the light box 410 may display a confirmation page. Insome embodiments, the confirmation page may provide a summary 415 of thetransaction. For example, the payment option selected, the itempurchased and the amount that was charged may be displayed to provideconfirmation to the user that the purchase is complete. Otherinformation such as more information on the UltimatePay 416 may also beprovided on the same confirmation page view. In the confirmation pageview, a continue button 417 may also be provided to allow the user toreturn back to the page where he or she was previously on. In this way,the light box 410 may provide an integrated way to conduct a transactionusing a variety of payment options from anywhere on a website and allowthe user to return back to his or activity seamlessly.

With reference to FIG. 4C, in some embodiments, the PAYPAL option may beselected by the user from the variety of payment options 412 availableto conduct a transaction. When the PAYPAL option is selected, a userinterface 418 customized for PAYPAL may be displayed to the user. Theamount due may be pre-populated and a “check out with PALPAL” button 419may be provided. Once the user clicks on the button 419, a customizedinterface 420, as shown in FIG. 4D, may be provided within the light boxshowing payment information for user confirmation. The interface 420 maydisplay purchase information 421 including description of the item(s) tobe purchased, payment amount, payment method (e.g., PALPAL balance),payment currency, applicable discounts, and/or the like. The interface420 may also include shipping and contact information 422. Once the userreviews the displayed information and makes any necessary changes, theuser may confirm payment with the “pay now” button 423. This mayconclude the transaction and a message 424 may be displayed informingthe user that the user will be returned to the web page he or she waspreviously on before initiating the transaction (e.g., the PlaySpanmarketplace). The user may also have the option to manually close thewindow and return to the previous web page.

With reference to FIG. 4E, in some embodiments, facilities may beprovided by customizing the payment light box with different skins,payment options, logos, advertisement, and/or the like as shown by lightboxes 425 and 426. Such customizations may provide the appearance of apayment system that is seamlessly integrated with the merchant.

FIGS. 5A-C show user interface diagrams illustrating example features ofdynamic payment optimization and virtual currency configuration, as partof providing flexible monetization services, in some embodiments of theDPO. In some embodiments, the DPO may facilitate optimization of thedisplay and presentation of the most relevant payment options to a userbased on parameters such as their country, age and purchasing behaviorof users with similar transactional history. The DPO may include aselection engine that utilizes information gained from a payment gatewayto get user behavior across different regions, age groups, locale, andapplications (ecommerce websites, or sections of a website, or games).At an aggregate level, patterns of behavior across differentapplications may be used predictably by the DPO to select the mostoptimal payment list for a optimizing the users propensity to pay.Variety of attributes associated with a “user profile” in addition tospecific regional requirements, may be used to generate simple patternsfor mapping new what new users are shown. For example, the DPO may knowthe most optimal payment list for 18-20 year olds playing strategy gameshistorically and therefore may present those methods to a new user inthat demographic. It further may refine that with regional informationfor 18-20 year old users from VS playing strategy games. Feedback in theform of users' input back to the DPO in turns of purchasing activitiesmay allow the selection engine to self refine the component of thepayments system and continually present optimal payment methods. Allpayment activities (anything from launching a payments application andabandoning to launching and making a payment) may be characterized byone or more attributes. Some attributes may be related to user profileinformation (locale, age, familiarity with the application, etc.), somemay be application specific (game type, social dimensions, paymentinformation/required, etc.), or region specific (what payment methodscategorically convert better in different regions). All these attributesmay be used to create patterns of behavior which ultimately result in anumber of actions (abandoning application somewhere in the completionfunnel, successfully finishing the payment process or starting over withsome changes to the input). Mapping all of that data to the paymentsthat were presented may give weight to accuracy of that presentedselection list.

The presentation of the payment options can be displayed to the user ona merchant in a number of ways. In some embodiments, when a merchantwishes to present a user with a payment option, the merchant may send aquery or API call to the payment provider that contains certain userdemographic information such as age, location, item to be purchased,social networking ID or many others. The payment processing system maythen compute, based on its algorithms and historic data, which paymentmethods are most likely to be the ones that will have the user completea transaction. In one embodiment, the DPO may generate an API list thatthe merchant receives for the recommended order list of payment methodto display to users. This API can further include graphics such aspayment logos, or know payment methods of a user such as for example aVisa Credit card ending with the last 4 digits of ABCD. In anotherembodiment, the merchant may integrate a payment widget, lightbox,web-redirect or iframe to allow the payment processor to directlyoptimize the VI and front end user experience of the display of themethods. This could be through a simple list, or through a tabbed basedapproach. In the tab based approach the tabs selected and the methodsthat are shown by default may dynamically change based on the usersdemographic information. In some embodiments, the DPO can furtheroptimize the purchasing experience by adjusting language, price points,currencies, merchandizing (such as promotions or display ads) or theuser interface and look and feel of the payment experience for the user.In general, the DPO may tailor the purchasing experience dynamically foreach individual user and can optimize and adjust a variety of parameterssuch as those listed above in order to create an experience that is mostlikely to have a user complete a transaction.

The DPO can also favor particular payment methods if the merchantdesires them to be given prominent placement if there are economicreasons or strategic preferences for favoring particular methods. Onemethod that might be favored is an existing account balance of storedcurrency that the user already has. By presenting the stored currency asa payment option ahead of other payment options, users can complete thetransaction with a simple one click and the merchant can then recognizethe revenues from the utilization of the stored balance.

In some embodiments, as shown in FIG. 5A, facilities may be provided forcustomizing payment options according to geography (e.g., continent,country, region, etc.) 511 a, language and/or the like. For example, thecountry Germany 511 b may be pre-selected or chosen by a user. Based onthe selected country, payment options, language and currency informationmay be automatically updated to cater to the users of the selectedcountry. For example, in the case of Germany, language may be German orany of the world's most spoken languages 512. Similarly, payment optionsmay be updated to show most popular payment methods in Germany or thehighest converting payment methods 513 in Germany. In a furtherimplementation, the interface may also be updated to display localizedcurrencies and price points 514.

With reference to FIG. 5B, an exemplary payment interface customized forthe selected country Japan 521 is provided. While credit and/or debitcard options such as VISA and AMERICAN EXPRESS and PAYPAL may beacceptable forms of payment in Japan or accepted by merchants, othercountry-specific payment choices 523 may also be provided under “morechoices” tab 522 in the payment interface. The user may then select anyof the provided choices for completing the transaction.

With reference to FIG. 5C, in some embodiments, payment options andordering in mobile application interfaces may also be customized basedon geography. When the United States is selected as the country 531, theamount due 632 a may be displayed in the currency of the United States.Various payment options in the mobile application may displayed in anarrangement customized for (or in some instances by the user) in theregion 533 a on the mobile application interface. When the countryselection is changed to Germany 531 b from the United States, the amountdue 532 b may displayed in local or popular currency. Similarly, variouspayment options and orderings may be modified as shown in the region 533b of the mobile application interface. In some embodiments, the highestconverting payment methods may be provided. In another implementation,the user may configure the settings for a country and may save it forfuture use.

With reference to FIG. 5D, in some embodiments, various currencyconfigurations may also be available in mobile interfaces of the paymentsystem. For example, a user may use Visa 542 a to pay for an amount due541 a in United States currency. In a further implementation, the usermay also have the option to pay for the amount (or a portion thereof)using rewards points 542 b. The corresponding amount due may bedisplayed in currency points at 541 b.

FIGS. 6A-D show user interface diagrams illustrating example features ofgeographic transaction volume analytics in some embodiments of the DPO.The DPO, in some embodiments, may provide online merchant with servicesto visualize the geographic payment volumes through the display of acountry heat map graph with configurable parameters to highlightdifferent features of the payment distribution.

In some embodiments, the DPO may enable users to view their paymentsfrom users on a country-by-country basis, understanding market share forcountries, e.g. US is 10% and Canada is 3%, total users, total paymentsand average payment size. These analytics and insights may givemerchants clues that they need to increase revenue streams in theircommerce activities. Additionally this data may be provided graphicallyshowing a global heat map with countries having more payments with adarker color and payments with few payments with a lighter color (or nocolor for no payments). The levels, color contrast and granularity ofthe map can be configured and may provide merchants with simple andquick ways to visualize the effectiveness of their commerce activitiesacross geographic regions.

In some embodiments, the geographies shown are country maps and thelevels of payments are segmented into five spectrums based on anexponential scale such that each darker color level represents twice thepayment volume than the next level. In some embodiments, the map may bedivided into states, cities or districts and the color gradient can be alinear spectrum from light to dark and normalized to from the lowestpaying location to the highest paying location, The graphical displaymay be populated, in one example, as follows: Each order and paymenttransaction may be tagged with an IP address and country stamp.Geopayments reports then created by the payment network by filtering alltransactions for a given merchant, then aggregated by country, andcounting the sum of users and transactions and calculating the countrymarket share and average payment size. Graphic charts may be created bytaking a map of the globe, aggregating payment volume and coloringdifferent countries based on the market share of payments in thatspecific country.

Various analytics facilities may be available for merchants having thepayment application integrated with their websites. An example merchantanalytics dashboard 610, as shown in FIG. 6A, may include variousoptions for generating graphical and other representations 616 ofanalytics such as geographic transaction volume. Example optionsavailable for configuration include, without limitation, type of data611 (e.g., users and transactions), service codes 612 (e.g., UT01—PBCTest Merchant), date range 613 (e.g., Sep. 20, 2010 to Oct. 20, 2010),frequency (e.g., daily, weekly, monthly, etc.), and/or the like toobserve trends for users and transactions over time. The graphicaldisplay area 616 may further display the trends for transactions 617 andusers 618 in graphical charts such as trend line and bar chart amongothers. The merchant may also change any of the parameters on thedashboard 610 on the fly, and click on update button 615 to generate agraphics for the updated parameters. In a further implementation, email619, download or export facilities may also be available for themerchant to download raw or processed data in EXCEL, text, WORD, .CSVand other formats, as well as graphics in various graphic formats suchas .bmp, .jpg, .jpeg/, .png, .gif, .PDF, and/or the like.

With reference to FIG. 6B, in some embodiments, the merchant mayreconfigure his or her dashboard to select other data types such asrevenue by payment method 621. The merchant may also select anotherservice code 622, data range 623 and frequency 624. When the merchantclicks on the update button 625, updated graphical charts may bedisplayed on the graphical display area 626. For example, for therevenue for payment method data 621, a pie chart 627 may be displayedshowing a percentage breakdown of revenue for each payment method.Further a line chart 628 may also be displayed showing the daily revenueamount (y-axis) for each payment method over a period of time (x-axis)defined by the date range 623. As in FIG. 6A, raw and/or processed dataand graphics may be available for email 629, export or download.

With reference to FIG. 6C, in some embodiments, a merchant may selectrevenue by country 631 data analysis. The merchant may also specifyservice codes 632, date range 633 and frequency 634. Once the updatebutton 635 is clicked, the graphical display area may display variousgraphical charts and maps showing revenue breakdown by country. Forexample, the heat map 637 may identify, using color or other indicators,each country which produced a revenue in the range of 0-5%, 5-10%,10-25%, 25-50% and higher than 50% during the defined time period. Otherpercentage ranges for revenue breakdown are contemplated and are withinthe scope of the payment system analytics. As another example, thegraphical chart 638 may show the revenue amount (y-axis) over a periodof time (x-axis) for each revenue producing country.

With reference to FIG. 6D, in some embodiments, various dashboard 640,analytics 641, customer service 642, manage systems 643 and mobile apps644 facilities may be integrated together in a single console. Themerchant (or service user in general) may log in and select any one ofthe tabs 640-644 to obtain analytics and information and manage variousservices, systems and mobile applications. For example, when thedashboard tab is selected, an overview of various analyses, data andcharts may be provided. For example, sub-windows such as geopayments645, revenue 646, conversion 647 and summary 648 may be displayed. Thesummary table 648, as shown, may include various columns of data such asdate 648 a, revenue 648 b, users 648 c, transactions 648 d, averagespending per user 648 e, average amount per transaction 648 f,conversion rate 648 g, and/or the like. In one implementation, thesummary table may include data for a predefined time period (e.g.,current month, current week). The data from the summary table may thenbe displayed using graphical charts in sub-windows such as thegeopayments sub-window 645, revenue 646 sub-window and conversionsub-window 647. The geopayments sub-window 646 may display geographicalheat maps of revenue described in FIG. 6C. The revenue window maydisplay a column chart of revenue amount 648 b (y-axis) plotted againstdate 648 a (x-axis). Similarly, the conversion sub-window 647 maydisplay a column chart that shows revenue 648 b on the left y-axis andconversion rate on the right y-axis plotted again date 648 a on thex-axis. In addition to the heat maps and column charts a describedabove, other types of graphical display techniques may be used. In afurther implementation, the “view reports” option on any of thesub-windows may be selected for further data analysis and/orreconfiguration of one or more parameters.

FIG. 7A-C show block and data flow diagrams illustrating an examplepurchase catalog browsing procedure in some embodiments of the DPO. Insome embodiments, the DPO may provide a foundation for merchandisingitems, subscriptions and other offers via a comprehensive and robuststorefront component that supports a global universal catalog. The DPOmay enable a merchant to manage multiple offerings, across multipleproperties (online and/or mobile) in multiple formats (in-game, widgets,social network-based applications, etc). Within this context, merchantsmay be able to manage up to thousands of items, price promotions,up-sell and cross-sell opportunities in a global setting with paymentand support in all areas. The DPO may provide a unique turn-key offeringthat leverages contextual offer management to drive higher conversion.The marketplace may be implemented in-game, on social networks and theweb or across all three. The full suite of merchandising tools, coupons,custom offers, bundles, promotional pricing, analytics, etc., providedby the DPO, may enable the merchant to maximize sales while providing ahigh quality experience to its customers. The DPO may provide featuressuch as, but limited to: Virtual currency wallet across games; One-clickpurchases; Recommendation engine; Catalog and offer management;Comprehensive customer service and analytical tools; and/or the like. Insome embodiments. The DPO may also enable merchants to profit fromadditional revenue streams as users transact among each other in anofficial and organized manner. These marketplaces may serve not only asadditional revenue streams, but also may increase stickiness to the siteby adding the social dimension of transaction and the promise ofprofiting from customer loyalty.

With reference to FIG. 7C, in some embodiments, a user, e.g., 701, maydesire to browse through a product catalog of a merchant managed by theDPO. The user may provide a catalog browsing input, e.g., 711, into apoint-of-sale (PoS) client, e.g., 702, to browse through a productcatalog. In various embodiments, the user input may include, but not belimited to: a single tap (e.g., a one-tap mobile app purchasingembodiment) of a touchscreen interface, keyboard entry, card swipe,activating a RFID/NFC enabled hardware device (e.g., electronic cardhaving multiple accounts, smartphone, tablet, etc.) within the userdevice, mouse clicks, depressing buttons on a joystick/game console,voice commands, single/multi-touch gestures on a touch-sensitiveinterface, touching user interface elements on a touch-sensitivedisplay, and/or the like. In response, the PoS client may generate aproduct search request, e.g., 712, and provide the product searchrequest, e.g., 713, to a merchant/acquirer (“merchant”) server, e.g.,703 a. For example, the client may provide a product search request tothe merchant server as a HTTP(S) POST message including XML-formatteddata. An example listing of a product search request 713, substantiallyin the form of a HTTP(S) POST message including XML-formatted data, isprovided below:

POST /productsearchrequest.php HTTP/1.1 Host: www.merchant.comContent-Type: Application/XML Content-Length: 229 <?XML version = “1.0”encoding = “UTF-8”?> <product_search_request>  <request_ID>PT456</request_ID>   <session_ID>ASDF3245678</session_ID>  <user_ID>john.q.public</user_ID>   <timestamp>2010-09-0921:21:21</timestamp>   <search_keys>type:virtual genre:actionbrand:sony</search_keys> </product_search_request>

In some embodiments, the merchant server may utilize the DPO to searchthrough the merchant's inventory to respond to the user's productcatalog browse request. The merchant server may provide a product searchrequest, e.g., 714, to a Monetization-as-a-Service (“MaaS”) server,e.g., 704 a. For example, the merchant server may generate anapplication programming interface call to request the MaaS server toprovide product catalog search results. For example, the client mayprovide a product search request to the MaaS server as a HTTP(S) POSTmessage including XML-formatted data. An example listing of a productsearch request 714, substantially in the form of a HTTP(S) POST messageincluding XML-formatted data, is provided below:

POST /productsearchrequest.php HTTP/1.1 Host: www.paygateway.comContent-Type: Application/XML Content-Length: 328 <?XML version = “1.0”encoding = “UTF-8”?> <product_search_request>  <request_ID>YTUERWTQRT</request_ID>  <session_ID>ASDF3245678</session_ID>   <timestamp>2010-09-0921:21:21</timestamp>   <search_keys>type:virtual genre:actionbrand:sony</search_keys>   <!--optional data-->    <user_ID>john.q.public</user_ID>    <merchant_ID>DFSG43564</merchant_ID> </product_search_request>

In some embodiments, the MaaS server may utilize a social networkservice to determine products to recommend for the user. In someembodiments, the MaaS server may request the user 701 to log into thesocial networking service in order to enable the user social graphsearch. For example, the MaaS server may request the social networkingservice to provide information on the user's communications on thesocial networking service, the user's social graph, and/or the socialnetworking communications of the members of the user's social graph onthe social networking service, e.g., 715. For example, the MaaS servermay execute a PHP script to generate an application interfaceprogramming call to the social network server. An example listing ofcommands to generate a user social graph search request 715, writtensubstantially in the form of PHP commands, is provided below:

<?PHP header(‘Content-Type: text/plain’); // Obtain user ID(s) offriends of the logged-in user $friends =  json_decode(file_get_contents(′https://graph.facebook.com/  me/friends?access   token=’$cookie[‘oauth_access_token′]), true);$friend_ids = array_keys($friends); // Obtain message feed associatedwith the profile of the logged-in user $feed =  json_decode(file_get_contents(′https:llgraph.facebook.com/me/  feed?access_token =′$cookie[′oauth_access_token′]), true); // Obtainmessages by the user's friends $result = mysql_query(′SELECT * FROMcontent WHERE uid IN   (′.implode($friend_ids, ′,′) . ′)′);$friend_content = array( ); while ($row = mysql_fetch_assoc($result))$friend_content [ ] $row;

In response, the social networking server may query, e.g., 716, its owndatabase (e.g., social network database 705 b), and obtain the requestedsocial search results, e.g., 717, from its database. The socialnetworking server may provide the retrieved information for the MaaSserver, e.g., user social graph search results 718. For example, thesocial networking server may provide a JavaScript Object Notation format(“JSON”)-encoded data structure embodying the requested information. Anexemplary JSON-encoded data structure embodying social data (e.g., userID(s) of friends of the logged-in user) is provided below:

[  “data”: [ { “name”: “Tabatha Orloff”, “id”: “483722”}, { “name”:“Darren Kinnaman”, “id”: “86S743”}, { “name”: “Sharron Jutras”, “id”:“O91274”} ]  }

In some embodiments, the MaaS server may query, e.g., 719, its owndatabase, e.g., MaaS database 704 b, for products matching the productssearch request key terms. In some embodiments, the merchant server mayobtain product catalog data, e.g., 720, such as product information,product pricing, sales tax, offers, discounts, rewards, and/or otherinformation to process the purchase transaction and/or providevalue-added services for the user. For example, the MaaS database may bea relational database responsive to Structured Query Language (“SQL”)commands. The MaaS server may execute a hypertext preprocessor (“PHP”)script including SQL commands to query a database table (such as FIG.23, Products 2319 l) for product data. An example product catalog query719, substantially in the form of PHP/SQL commands, is provided below:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.93.179.112”,$DBserver,$password); // access databaseserver mysql_select_db(“DPO_DB.SQL”); // select database table to search//create query $query = “SELECT product_title product_attributes_listproduct_price   tax_info_list related_products_list offers_listdiscounts_list   rewards_list merchants_list merchant_availability_listFROM   ProductsTable WHERE product_ID LIKE ‘%’ $prodID”; $result =mysql_query($query); // perform the search querymysql_close(“DPO_DB.SQL”); // close database access ?>

In some embodiments, the MaaS server may generate a product searchresponse using the product catalog data and user social graph searchresults, e.g., 721. The MaaS server may provide the product searchresponse, e.g., 722, to the merchant server as a response to themerchant server's product search request 714. For example, the MaaSserver may provide the product search response to the merchant server asa HTTP(S) POST message including XML-formatted data. An example listingof a product search response 722, substantially in the form of a HTTP(S)POST message including XML-formatted data, is provided below:

POST /productsearchresponse.php HTTP/1.1 Host: www.merchant.comContent-Type: Application/XML Content-Length: 1038 <?XML version = “1.0”encoding = “UTF-8”?> <product_search_response>  <request_ID>YTUERWTQRT</request_ID>  <session_ID>ASDF3245678</session_ID>   <timestamp>2010-09-0921:21:21</timestamp>   <search_keys>type:virtual genre:actionbrand:sony</search_keys>   <expiry_lapse>00:03:00</expiry_lapse>  <response_details>      <num_products>1</num_products>      <product>        <product_type>book</product_type>         <product_params>           <product_title>XML for dummies            </product_title>           <ISBN>938-2-14-168710-0</ISBN>            <edition>2nded.</edition>            <cover>hardbound</cover>           <seller>bestbuybooks</seller>         </product_params>        <quantity>1</quantity>      </product>   </purchase_details>  <offers_details>      <num_offers>1</num_offers>      <product>        <product_type>book</product_type>         <product_params>           <product_title>Here's more XML            </product_title>           <ISBN>922-7-14-165720-1</ISBN>            <edition>1nded.</edition>            <cover>hardbound</cover>           <seller>digibooks</seller>         </product_params>        <quantity>1</quantity>      </product>   </offers_details></product_search_response>

In some embodiments, the merchant server may provide the product searchresponse, e.g., 723, to the PoS client, which may display, e.g., 724,the product search results to the user. In some embodiments, the usermay select a product from among the displayed products for purchase. Theuser may provide a product selection input, e.g., 725, to indicate theuser's desire to obtain the product. The PoS client may generate aproduct cart request, e.g., 726, and provide the product cart request,e.g., 727, to the merchant server, in response to obtaining the user'sproduct selection input. For example, the PoS client may generate aHTTP(S) POST message similar to the example above, and provide it to themerchant server. The merchant server may query its database, e.g., 728,for prior product cart data, e.g., 729. For example, it may execute ahypertext preprocessor (“PHP”) script including SQL commands to query adatabase table (such as FIG. 23, Products 2319 l) for product cart data.An example product cart data query 728, substantially in the form ofPHP/SQL commands, is provided below:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.93.179.112”,$DBserver,$password); // access databaseserver mysql_select_db(“DPO_DB.SQL”); // select database table to search//create query $query = “SELECT product_title product_attributes_listproduct_price   tax_info_list merchants_list merchant_availability_listFROM   ProductsTable WHERE session_ID LIKE ‘%’ $sessionID”; $result =mysql_query($query); // perform the search querymysql_close(“DPO_DB.SQL”); // close database access ?>

In some embodiments, upon obtaining the product cart data, e.g., 729,the merchant server may generate updated product data based on theproduct cart request, e.g., 730, and store the updated product cart datain the merchant database, e.g., 731. For example, the merchant servermay issue PHP/SQL commands to store the data to a database table (suchas FIG. 23, Products 2319 l). An example updated product cart storecommand 731, substantially in the form of PHP/SQL commands, is providedbelow:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(″254.92.185.103”,$DBserver,$password); // access databaseserver mysql_select(″DPO_DB.SQL″); // select database to appendmysql_query(“INSERT INTO ProductsTable (session_id, product_title,  product_attributes_list, product_price, tax_info_list,  merchants_list, merchant_availability_list) VALUES ($session_id$product_title $product_attributes_list   $product_price $tax_info_list$merchants_list   $merchant_availability_list)”); // add data to tablein database mysql_close(″DPO_DB.SQL″); // close connection to database?>

FIG. 8 shows a logic flow diagram illustrating example aspects ofpurchase catalog browsing in some embodiments of the DPO, e.g., aPurchase Catalog Browsing (“PCB”) component 800. In someimplementations, a user may desire to browse through a product catalogof a merchant managed by the DPO. The user may provide a catalogbrowsing input, e.g., 801, into a point-of-sale (PoS) client to browsethrough a product catalog. In various embodiments, the user input mayinclude, but not be limited to: a single tap (e.g., a one-tap mobile apppurchasing embodiment) of a touchscreen interface, keyboard entry, cardswipe, activating a RFID/NFC enabled hardware device (e.g., electroniccard having multiple accounts, smartphone, tablet, etc.) within the userdevice, mouse clicks, depressing buttons on a joystick/game console,voice commands, single/multi-touch gestures on a touch-sensitiveinterface, touching user interface elements on a touch-sensitivedisplay, and/or the like. In response, the PoS client may generate aproduct search request, e.g., 802, and provide the product searchrequest to a merchant/acquirer (“merchant”) server. In some embodiments,the merchant server may utilize the DPO to search through the merchant'sinventory to respond to the user's product catalog browse request. Themerchant server may provide a product search request to a MaaS server.For example, the merchant server may generate an application programminginterface call to request the MaaS server to provide product catalogsearch results, e.g., 803. In some embodiments, the MaaS server mayutilize a social network service to determine products to recommend forthe user. In some embodiments, the MaaS server may request the user tolog into the social networking service in order to enable the usersocial graph search. For example, the MaaS server may request the socialnetworking service to provide information on the user's communicationson the social networking service, the user's social graph, and/or thesocial networking communications of the members of the user's socialgraph on the social networking service, e.g., 804. In response, thesocial networking server may query its own database, e.g., 805, andobtain the requested social search results from its database, e.g., 806.The social networking server may provide the retrieved information forthe MaaS server, e.g., 807.

In some embodiments, the MaaS server may query its own database forproducts matching the products search request key terms, e.g., 808. Insome embodiments, the merchant server may obtain product catalog data,such as product information, product pricing, sales tax, offers,discounts, rewards, and/or other information to process the purchasetransaction and/or provide value-added services for the user. In someembodiments, the MaaS server may generate a product search responseusing the product catalog data and user social graph search results,e.g., 810. The MaaS server may provide the product search response tothe merchant server as a response to the merchant server's productsearch request.

In some embodiments, the merchant server may provide the product searchresponse to the PoS client, e.g., 811, which may display the productsearch results to the user, e.g., 812. In some embodiments, the user mayselect a product from among the displayed products for purchase, e.g.,813. The user may provide a product selection input to indicate theuser's desire to obtain the product. The PoS client may generate aproduct cart request, e.g., 814, and provide the product cart request tothe merchant server, in response to obtaining the user's productselection input. In some embodiments, upon obtaining the product cartdata, the merchant server may generate updated product data based on theproduct cart request, e.g., 815-817, and store the updated product cartdata in the merchant database, e.g., 818.

FIG. 9 shows a data flow diagram illustrating an example user purchasecheckout procedure in some embodiments of the DPO. In some embodiments,a user, e.g., 901 a, may desire to purchase a product, service,offering, and/or the like (“product”), from a merchant via a merchantonline site or in the merchant's store. The user may communicate with amerchant/acquirer (“merchant”) server, e.g., 903 a, via a client suchas, but not limited to: a personal computer, mobile device, television,point-of-sale terminal, kiosk, ATM, and/or the like (e.g., 902). Forexample, the user may provide user input, e.g., checkout input 911, intothe client indicating the user's desire to purchase the product. Invarious embodiments, the user input may include, but not be limited to:a single tap (e.g., a one-tap mobile app purchasing embodiment) of atouchscreen interface, keyboard entry, card swipe, activating a RFID/NFCenabled hardware device (e.g., electronic card having multiple accounts,smartphone, tablet, etc.) within the user device, mouse clicks,depressing buttons on a joystick/game console, voice commands,single/multi-touch gestures on a touch-sensitive interface, touchinguser interface elements on a touch-sensitive display, and/or the like.As an example, a user in a merchant store may scan a product barcode ofthe product via a barcode scanner at a point-of-sale terminal. Asanother example, the user may select a product from a webpage catalog onthe merchant's website, and add the product to a virtual shopping carton the merchant's website. The user may then indicate the user's desireto checkout the items in the (virtual) shopping cart. For example, theuser may activate a user interface element provided by the client toindicate the user's desire to complete the user purchase checkout. Theclient may generate a checkout request, e.g., 912, and provide thecheckout request, e.g., 913, to the merchant server. For example, theclient may provide a (Secure) Hypertext Transfer Protocol (“HTTP(S)”)POST message including the product details for the merchant server inthe form of data formatted according to the eXtensible Markup Language(“XML”). An example listing of a checkout request 912, substantially inthe form of a HTTP(S) POST message including XML-formatted data, isprovided below:

POST /checkoutrequest.php HTTP/1.1 Host: www.merchant.com Content-Type:Application/XML Content-Length: 667 <?XML version = “1.0” encoding =“UTF-8”?> <checkout_request>   <checkout_ID>4NFU4RG94</checkout_ID>  <timestamp>2011-02-22 15:22:43</timestamp>   <purchase_detail>     <num_products>5</num_products>     <product_ID>AE95049324</product_ID>     <product_ID>MD09808755</product_ID>     <product_ID>OC12345764</product_ID>     <product_ID>KE76549043</product_ID>     <product_ID>SP27674509</product_ID>   </purchase_detail><!--optional parameters-->   <user_ID>john.q.public@gmail.com</user_ID>  <PoS_client_detail>      <client_IP>192.168.23.126</client_IP>     <client_type>smartphone</client_type>      <client_model>HTCHero</client_model>      <OS>Android 2.2</OS>     <app_installed_flag>true</app_installed_flag>  </PoS_client_detail> </checkout_request>

In some embodiments, the merchant server may obtain the checkout requestfrom the client, and extract the checkout detail (e.g., XML data) fromthe checkout request. For example, the merchant server may utilize aparser such as the example parsers described below in the discussionwith reference to FIG. 23. Based on parsing the checkout request 912,the merchant server may extract product data (e.g., productidentifiers), as well as available PoS client data, from the checkoutrequest. In some embodiments, using the product data, the merchantserver may query, e.g., 914, a merchant/acquirer (“merchant”) database,e.g., 903 b, to obtain product data, e.g., 915, such as productinformation, product pricing, sales tax, offers, discounts, rewards,and/or other information to process the purchase transaction and/orprovide value-added services for the user. For example, the merchantdatabase may be a relational database responsive to Structured QueryLanguage (“SQL”) commands. The merchant server may execute a hypertextpreprocessor (“PHP”) script including SQL commands to query a databasetable (such as FIG. 23, Products 2319 l) for product data. An exampleproduct data query 914, substantially in the form of PHP/SQL commands,is provided below:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.93.179.112”,$DBserver,$password); // access databaseserver mysql_select_db(“DPO_DB.SQL”); // select database table to search//create query $query = “SELECT product_title product_attributes_listproduct_price   tax_info_list related_products_list offers_listdiscounts_list   rewards_list merchants_list merchant_availability_listFROM   ProductsTable WHERE product_ID LIKE ‘%’ $prodID”; $result =mysql_query($query); // perform the search querymysql_close(“DPO_DB.SQL”); // close database access ?>

In some embodiments, in response to obtaining the product data, themerchant server may generate, e.g., 916, checkout data to provide forthe PoS client. In some embodiments, such checkout data, e.g., 917, maybe embodied, in part, in a HyperText Markup Language (“HTML”) pageincluding data for display, such as product detail, product pricing,total pricing, tax information, shipping information, offers, discounts,rewards, value-added service information, etc., and input fields toprovide payment information to process the purchase transaction, such asaccount holder name, account number, billing address, shipping address,tip amount, etc. In some embodiments, the checkout data may be embodied,in part, in a Quick Response (“QR”) code image that the PoS client candisplay, so that the user may capture the QR code using a user's deviceto obtain merchant and/or product data for generating a purchasetransaction processing request. In some embodiments, a user alertmechanism may be built into the checkout data. For example, the merchantserver may embed a URL specific to the transaction into the checkoutdata. In some embodiments, the alerts URL may further be embedded intooptional level 3 data in card authorization requests, such as thosediscussed further below with reference to FIGS. 15-16. The URL may pointto a webpage, data file, executable script, etc., stored on themerchant's server dedicated to the transaction that is the subject ofthe card authorization request. For example, the object pointed to bythe URL may include details on the purchase transaction, e.g., productsbeing purchased, purchase cost, time expiry, status of order processing,and/or the like. Thus, the merchant server may provide to the paymentnetwork the details of the transaction by passing the URL of the webpageto the payment network. In some implementations, the payment network mayprovide notifications to the user, such as a payment receipt,transaction authorization confirmation message, shipping notificationand/or the like. In such messages, the payment network may provide theURL to the user device. The user may navigate to the URL on the user'sdevice to obtain alerts regarding the user's purchase, as well as otherinformation such as offers, coupons, related products, rewardsnotifications, and/or the like. An example listing of a checkout data917, substantially in the form of XML-formatted data, is provided below:

<?XML version = “1.0” encoding = “UTF-8”?> <checkout_data>  <session_ID>4NFU4RG94</session_ID>   <timestamp>2011-02-2215:22:43</timestamp>   <expiry_lapse>00:00:30</expiry_lapse>  <transaction_cost>$34.78</transaction_cost>  <alerts_URL>www.merchant.com/shopcarts.php?sessionID=  4NFU4RG94</alerts_URL>   <!--optional data-->  <user_ID>john.q.public@gmail.com</user_ID>   <client_details>     <client_IP>192.168.23.126</client_IP>     <client_type>smartphone</client_type>      <client_model>HTCHero</client_model>      <OS>Android 2.2</OS>     <app_installed_flag>true</app_installed_flag>   </client_details>  <purchase_details>      <num_products>1</num_products>      <product>        <product_type>book</product_type>         <product_params>           <product_title>XML for dummies            </product_title>           <ISBN>938-2-14-168710-0</ISBN>            <edition>2nded.</edition>            <cover>hardbound</cover>           <seller>bestbuybooks</seller>         </product_params>        <quantity>1</quantity>      </product>   </purchase_details>  <offers_details>      <num_offers>1</num_offers>      <product>        <product_type>book</product_type>         <product_params>           <product_title>Here's more XML            </product_title>           <ISBN>922-7-14-165720-1</ISBN>            <edition>1nded.</edition>            <cover>hardbound</cover>           <seller>digibooks</seller>         </product_params>        <quantity>1</quantity>      </product>   </offers_details>  <secure_element>www.merchant.com/securedyn/0394733/123.png  </secure_element>   <merchant_params>     <merchant_id>3FBCR4INC</merchant_id>      <merchant_name>Books &Things, Inc.</merchant_name>     <merchant_auth_key>1NNF484MCP59CHB27365      </merchant_auth_key>  </merchant_params> <checkout_data>

In alternate embodiments, the merchant server may invoke a component togenerate checkout data, such as the example flexible monetizationservice component discussed below with reference to FIGS. 11-12. Uponobtaining the checkout data, e.g., 917, the PoS client may render anddisplay, e.g., 918, the checkout data for the user.

FIG. 10 shows a logic flow diagram illustrating example aspects of userpurchase checkout in some embodiments of the DPO, e.g., a User PurchaseCheckout (“UPC”) component 1000. In some embodiments, a user may desireto purchase a product, service, offering, and/or the like (“product”),from a merchant via a merchant online site or in the merchant's store.The user may communicate with a merchant/acquirer (“merchant”) servervia a PoS client. For example, the user may provide user input, e.g.,1001, into the client indicating the user's desire to purchase theproduct. The client may generate a checkout request, e.g., 1002, andprovide the checkout request to the merchant server. In someembodiments, the merchant server may obtain the checkout request fromthe client, and extract the checkout detail (e.g., XML data) from thecheckout request. For example, the merchant server may utilize a parsersuch as the example parsers described below in the discussion withreference to FIG. 23. Based on parsing the checkout request, themerchant server may extract product data (e.g., product identifiers), aswell as available PoS client data, from the checkout request. In someembodiments, using the product data, the merchant server may query,e.g., 1003, a merchant/acquirer (“merchant”) database to obtain productdata, e.g., 1004, such as product information, product pricing, salestax, offers, discounts, rewards, and/or other information to process thepurchase transaction and/or provide value-added services for the user.In some embodiments, in response to obtaining the product data, themerchant server may generate, e.g., 1005, checkout data to provide,e.g., 1006, for the PoS client. In some embodiments, the merchant servermay invoke a component to generate checkout data, such as the exampleflexible monetization service component discussed below with referenceto FIGS. 11-12. Upon obtaining the checkout data, the PoS client mayrender and display, e.g., 1007, the checkout data for the user.

FIGS. 11A-B show data flow diagrams illustrating an example flexiblemonetization service procedure in some embodiments of the DPO. In someembodiments, a merchant server or other entity or component within theDPO may obtain a trigger, e.g., 1111, to provide flexible monetizationservices (see, e.g., FIG. 9, 916). In some embodiments, the merchantserver may parse the obtained trigger for providing P2P social networkmarketing service, and extract details of services required by themerchant to service the trigger. For example, the merchant may requireto provide checkout services, including configuration the UI of thecheckout page for the user, configuring the currency in which thepurchase price is displayed in currencies available to the user, and/orthe like. The merchant server may identify the services required to beperformed to service the flexible monetization service trigger, andgenerate, e.g., 1112, a flexible monetization service request based onidentifying the required services. The merchant server may provide,e.g., 1113, the flexible monetization service request to a MaaS server,e.g., 1104 a, for processing. For example, the merchant server mayprovide a flexible monetization service request to the MaaS server as aHTTP(S) POST message including XML-formatted data. An example listing ofa flexible monetization service request 1113, substantially in the formof a HTTP(S) POST message including XML-formatted data, is providedbelow:

POST /monetizationservicerequest.php HTTP/1.1 Host: www.paygateway.comContent-Type: Application/XML Content-Length: 1126 <?XML version = “1.0”encoding = “UTF-8”?> <flexible_monetization_service_request>  <session_ID>4NFU4RG94</order_ID>   <timestamp>2011-02-2215:22:43</timestamp>   <expiry>00:00:30</expiry>  <alerts_URL>www.merchant.com/shopcarts.php?sessionID=  AEBB4356</alerts_URL>   <!--optional data-->  <user_ID>john.q.public@gmail.com</user_ID>   <PoS_details>     <PoS_IP>192.168.23.126</client_IP>     <PoS_type>smartphone</client_type>      <PoS_model>HTCHero</client_model>      <OS>Android 2.2</OS>     <app_installed_flag>true</app_installed_flag>   </PoS_details>  <purchase_details>      <num_products>1</num_products>      <product>        <product_type>book</product_type>         <product_params>           <product_title>XML for dummies            </product_title>           <ISBN>938-2-14-168710-0</ISBN>            <edition>2nded.</edition>            <cover>hardbound</cover>           <seller>bestbuybooks</seller>         </product_params>        <quantity>1</quantity>      </product>   </purchase_details>  <merchant_params>      <merchant_id>3FBCR4INC</merchant_id>     <merchant_name>Books & Things, Inc.</merchant_name>     <merchant_auth_key>1NNF484MCP59CHB27365      </merchant_auth_key>  </merchant_params> <flexible_monetization_service_request>

In some embodiments, the MaaS server may, in response to obtaining theflexible monetization service request, determine whether themerchant-user combination is authorized to utilize flexible monetizationservices. For example, the MaaS server may query, e.g., 1114, a MaaSdatabase, e.g., 1104 b, to determine whether the merchant and/or userare authorized to receive its services, e.g., 1115. For example, theMaaS server may utilize PHP/SQL commands similar to those describedpreviously to determine service authorization. In some embodiments, theMaaS server may utilize the service authorization response, e.g., 1115,to identify, e.g., 1116, the services in which the merchant is enrolledwhich can be provided for the particular user shopping session for whichthe merchant obtained the flexible monetization service request. Upondetermining whether the user-merchant combination is authorized toreceive its services, the MaaS server may provide a serviceauthorization confirmation message (or retry message, if the MaaS serverdetermines that the session is not authorized for services), e.g., 1117,to the merchant server.

With reference to FIG. 11B, in some embodiments, the MaaS server mayidentify, among the enrolled services, the services associated with PoSnotification/offer generation, e.g., 1119. The MaaS server may obtainany service data, e.g., via PHP/SQL commands to its database asdescribed previously, to obtain the data necessary to perform theservices. The MaaS server may invoke components for each enrolledservice associated with PoS notification/offer generation, e.g., 1112.For example, the MaaS server may invoke the VCC 1300 and DPO 1400components described further below with reference to FIGS. 13 and 14respectively. Using the results of the invoked components, the MaaSserver may generate, e.g., 1123 a checkout widget customized to a userpurchase checkout session (e.g., a javascript or AJAX lightbox). Forexample, the MaaS server may generate a code listing similar to theexample code listing provided below as the checkout widget 1124:

<html>  <body>   <script type=“text/javascript”src=“http://static.pay.Com/js/   ultimatepay-api.js”></script>   <scripttype=“text/javascript”>   var ultimatePayParams = {    “sn” : “ACME”,   “userid” : “131827”,    “currency” : “USD”,    “sepamount” : “6.99”,   “amountdesc” : “Gold Membership”,    “hash” :“df659d502af5151a2edd18e2ebb50ba3”,    “xdurl” :“http://www.mydomain.com/xd.html”   }   // Merchant-defined function todisplay Lightbox.   function showLightbox( ) {     ulp.ultimatePay =true;   ulp.displayUltimatePay( );   }   </script>   <ahref=“javascript:showLightbox( );”>Pay Now</a>   <div id=“div_b”style=“display:none;padding:10px;position:absolute;   top: 50%;left:50%; margin-top: −212px; margin-left: −351px;”></div>  </body> </html>

In some embodiments, the MaaS server may provide the checkout widget,e.g., 1124, to the merchant server, which may provide the widget back tothe source of the trigger for flexible monetization services.

FIGS. 12A-B shows logic flow diagrams illustrating example aspects offlexible monetization service in some embodiments of the DPO, e.g., aFlexible Monetization Service (“FMS”) component 1200. In someembodiments, a merchant server or other entity or component within theDPO may obtain a trigger, e.g., 1201, to provide flexible monetizationservices (see, e.g., FIG. 9, 916). In some embodiments, the merchantserver may parse the obtained trigger for providing P2P social networkmarketing service, and extract details of services required by themerchant to service the trigger. For example, the merchant may requireto provide checkout services, including configuration the UI of thecheckout page for the user, configuring the currency in which thepurchase price is displayed in currencies available to the user, and/orthe like. The merchant server may identify the services required to beperformed to service the flexible monetization service trigger, andgenerate, e.g., 1202, a flexible monetization service request based onidentifying the required services. The merchant server may provide theflexible monetization service request to a MaaS server for processing.In some embodiments, the MaaS server may, in response to obtaining theflexible monetization service request, determine whether themerchant-user combination is authorized to utilize flexible monetizationservices. For example, the MaaS server may query, e.g., 1203, a MaaSdatabase to determine whether the merchant and/or user are authorized toreceive its services, e.g., 1204. For example, the MaaS server mayutilize PHP/SQL commands similar to those described previously todetermine service authorization. In some embodiments, the MaaS servermay utilize the service authorization response to identify, e.g., 1206,the services in which the merchant is enrolled which can be provided forthe particular user shopping session for which the merchant obtained theflexible monetization service request. Upon determining whether theuser-merchant combination is authorized to receive its services, theMaaS server may provide a service authorization confirmation message (orretry message, if the MaaS server determines that the session is notauthorized for services), e.g., 1207, to the merchant server.

With reference to FIG. 12B, in some embodiments, the MaaS server mayidentify, among the enrolled services, the services associated with PoSnotification/offer generation, e.g., 1209. The MaaS server may obtainany service data, e.g., via PHP/SQL commands to its database asdescribed previously, to obtain the data necessary to perform theservices, e.g., 1210-1211. The MaaS server may invoke components foreach enrolled service associated with PoS notification/offer generation,e.g., 1212-1213. For example, the MaaS server may invoke the VCC 1300and DPO 1400 components described further below with reference to FIGS.13 and 14 respectively. Using the results of the invoked components, theMaaS server may generate, e.g., 1214, a checkout widget customized to auser purchase checkout session (e.g., a javascript or AJAX lightbox). Insome embodiments, the MaaS server may provide the checkout widget, e.g.,1214, to the merchant server, which may provide the widget back to thesource of the trigger for flexible monetization services.

FIGS. 13A-F show block and logic flow diagrams illustrating exampleaspects of virtual currency configuration in some embodiments of theDPO, e.g., a Virtual Currency Configuration (“VCC”) component 1300. Insome embodiments, the DPO may allow for game developers to price andpackage their virtual currencies in multiple currencies and multiplepayment methods. Price packaging may allow game developers the abilityto specify ratios, discreet pricing and even “smart pricing”—which autorounds virtual currency bundles. For example, game developers mayconfigure virtual currency bundles. For example, one or more virtualcurrencies and/or currency management rules may be included in a virtualcurrency bundle, and wherein a discount level for any virtual currencybundle may vary based on a user-selected payment method, and a devicetype from where the user procures the virtual currency bundle. Forexample, a user purchasing using a preferred payment method such as aVisa credit card may be offered a currency bundle of $1 to 1000 virtualgame gold pieces, but only gold pieces were they to select a check as apayment mechanism. Also, merchants may incentivize or decentivize usersto obtain gold pieces through certain devices, applications, and/orother mechanisms. For example, when purchasing gold pieces within avirtual game, for instant in-game availability, a premium may be added,and the currency bundle may result in providing only 900 gold piecesinstead of 1000 gold pieces in the above example. In another examplewhere a merchant wishes to incentivize users to purchase virtualcurrency bundles on mobile devices, the merchant may provide 1250 goldpieces for the same $1. These virtual currency bundles may be specifiedby the merchant and/or other components and/or entities within the DPO.

In some embodiments, the DPO may manage ratios. For example, let's saythat a game wants to see virtual currency for a ratio of $1 to 100. TheDPO may automatically calculate virtual currency amounts, so that if youenter a payment for $5, then 500 points is automatically created.

In some embodiments, the DPO may manage Discreet Pricing. For example,let's say that a game wants to give away more coins for money invested.Discreet pricing allows game developers to enter discreet point packagesfor different prices points. For example, the user might get 500 coinsfor $5, but 1,100 coins for $10 (a 100 coin bonus).

In some embodiments, the DPO may utilize Smart Pricing. For example,let's say that a game sets a ratio of $1=1,000 coins. However, the useris in Germany and prefers to pay in Euros. Instead of just doing asimple conversion and showing 1 EUR=793 Coins, Game Developers can roundeither up or down, from 1-3 significant digits. This means that the usermight see 800 coins (rounded up to two significant digits) which is amuch better number than 793 (from a consumer marketing perspective). Insome embodiments, a setting for each country, merchant, and/or productmay specify the number of threshold digits that may be rounded. Forexample, in the US, aggregate analysis of consumer behavior may showthat two-digit rounding to enhance and increase transaction throughputfor 4-digit point levels. For example, if a strict conversion ratio for$10 would 1237 virtual coins, having a two-digit rounding for the4-digit value may result in an amount of 1250 coins, with “50” being thelast two digits allowed for threshold rounding.

In some embodiments, the DPO may adapt virtual currencies according tothe costs of the payment method employed by the user. As one example,the DPO may manage a high cost payment method such as Mobile Pricing.For example, let's say that a game sets a ratio of $1=1,000 coins forstandard payments, e.g. credit card or PayPal. What if the user wants topay in mobile? Mobile payments tend to charge 50% or more. The gamedeveloper can specify different ratios for different payment methods ordifferent payment cost types. In this example, the game developer mightwant to give the user $1=750 coins (25% less coins) to help cover theeconomic costs of the mobile payment. As another example, the gamedeveloper may utilize different discrete mobile price points acrossmultiple carriers, and set ratios (or discrete points) so that the DPOcan automatically calculate a discrete number of price points percarrier for each country and show the appropriate pricing to the user.In general, it is contemplated that a DPO may facilitate dividing up theavailable price points to maximize the range of payment options providedto the user, and then provide a set number of payment choices, andcalculating the applicable virtual currency to display.

In some embodiments, the DPO may accommodate the above mentioned virtualcurrency use cases as follows: Virtual Currencies may be created by thegame developer on a Developer Console. Virtual currencies may beconfigured with names, like “Coins” and virtual currency codes, whichreference the virtual currency during API calls. Once a virtual currencyhas been created, the game developer may create pricing rules for thevirtual currency.

In some embodiments, once a base set of rules is created—the virtualcurrency is ready for use. The game developer may sell the virtualcurrency on their service, and when the user clicks on “buy”; then thegame developer may also pass a virtual currency code, to let the DPOknow that the purchase is for a virtual currency configured in the DPO.The payment interface on the game developer's site may then allow theuser to make the payment. The interface may show price packages in dropdowns and buttons according to the rules set up in the developerconsole. When the payment is complete, the DPO may send a postbackcommunication to the game developer that the payment is complete. Aspart of the payment complete notification, the DPO may also pass thevirtual currency code (so the game developer knows to credit the userwith virtual currency), as well as the amount of virtual currency tocredit. For security both the virtual currency code and the virtualcurrency amount may be MD5 hashed, so that users can't tamper with orgrant themselves extra virtual currency.

With reference to FIG. 13F, in some embodiments, an entity and/orcomponent of the DPO may obtain a trigger for virtual currencyconfiguration (e.g., MaaS server 1104 a in FIG. 11A), e.g., 1301. As anexample, the DPO may obtain the trigger when a user requires on-demandmodification of payment options in a UI (see e.g., FIG. 3B). The DPO mayobtain data on the product being purchased for which virtual currencyconfiguration is sought, e.g., 1302. The DPO may identify a set ofcurrencies using which the user desires to pay for the product purchase,e.g., 1303. For example, if the user desires to pay 40% of the purchaseprice using rewards points, and 60% using Japanese yen, then the DPO mayidentify the specific type of rewards points and Japanese yen as the setof currencies to convert the purchase price into, from the presentcurrency(ies) in which the pricing information is available. Based onidentifying the set of currencies, the DPO may decompose the purchaseprice according to the share of identified currencies, e.g., 1304. Forexample, if the purchase price is $10, for the example set of currenciesabove, the DPO may decompose the purchase prices into $4 for paymentthrough rewards points, and $6 for payment through Japanese yen.

In some embodiments, the DPO may determine currency exchange rates forthe virtual currency configuration based on one or more factors, whichmay include, but not be limited to: user device platform (e.g., mobiledevice, online game, eCommerce site, shopping in physical store, etc.),user payment method (e.g., debit, credit, etc.), and/or the like. Forexample, the DPO may determine the user's platform using communicationsforwarded to it from the PoS client where the user is engaged in thepurchase transaction, e.g., 1305. The DPO may also determine the userpayment method being utilized for payment, e.g., using user paymentselections made by the user at the PoS client being utilized for thepurchase transactions, e.g., 1306. The DPO may determine a currencyconversion exchange rate for each of the set of currencies identified asbeing implicated in the virtual currency configuration. For example, theDPO may select a currency from the identified set of currencies forconversion, e.g., 1307. The DPO may query a database for a conversionalgorithm to utilize for the conversion, based on the user platform,payment method, selected currency, and/or the like. For example the DPOmay query a database using PHP/SQL commands similar to the exampledescribed previously to obtain the conversion algorithm to utilize.Several examples of conversion algorithms are described below. The DPOmay utilize any single algorithm, or combinations of the algorithms inany sequence and to any portion of the conversion of the set ofcurrencies, to convert the price from one currency to another

For example, one algorithm, a constant ratio algorithm, may assign aconstant exchange rate, regardless of the total value of the purchaseprice. A discreet pricing algorithm may assign a variable exchange ratedepending on the total value of the purchase price. For example, theexchange rate may be lowered (e.g., more beneficial to the user) whenthe total purchase price is higher than a threshold value, than when itthe total purchase price is lower than the threshold value. The discreetpricing algorithm may, in some embodiments, utilize a plurality ofthresholds to a generate virtual currency conversions. As anotherexample, one algorithm, a smart pricing algorithm, may round the valueof any input passed to it to at least one significant digit. The inputspassed to the smart pricing algorithm may, in various embodiments, bethe exchange rate calculated by another algorithm, a price calculated byanother algorithm, a (portion of a) purchase price of a product, and/orthe like. In some embodiments, the DPO may utilize a pre-specified tablefor performing some of the currency conversions. In such embodiments,the DPO may query a database for a conversion table for the identifiedcurrency conversions, using the user platform, payment method andconversion algorithms as keys for the query, e.g., 1309. Using theconversion algorithms and conversion tables, the DPO may compute aconversion currency equivalent of the share of the total purchase price.In some embodiments, the conversion currency equivalent may be roundedusing the smart pricing algorithm before being returned as a response tothe trigger. The DPO may perform such currency conversions for eachcurrency identified as belonging to the set of currencies implicated inthe virtual currency conversion. The DPO may return the conversioncurrency equivalents in a result data record as a response to theobtained trigger.

FIG. 14 shows a logic flow diagram illustrating example aspects ofdynamic payment optimization in some embodiments of the DPO, e.g., aDynamic Payment Optimization (“DPO”) component 1400. In someembodiments, an entity and/or component of the DPO may obtain a triggerfor dynamic payment optimization (e.g., MaaS server 1104 a in FIG. 11A),e.g., 1401. As an example, the DPO may obtain the trigger when a userrequires on-demand modification of payment options in a UI (see e.g.,FIG. 3B). The DPO may obtain a checkout request for which payment UI isto be optimized (see e.g., FIG. 9, 9 13), e.g., 1402. The DPO may parsethe checkout request, and identify user device attributes: type,orientation, screen size, resolution, etc., e.g., 1403. For example, theDPO may utilize parsers similar to the example parsers described belowwith reference to FIG. 23. The DPO may parse the checkout request, andidentify a user location (e.g., via IP address lookup), e.g., 1404. TheDPO may classify the location type of user's device location (e.g.,urban, rural, etc.), for example, based on an lookup of the IP addressof the user device, e.g., 1405. The DPO may query a database for a userprofile, and identify a set of user demographic(s), e.g., 1406. Forexample, the DPO may obtain demographic data such as, but not limitedto: age group, gender, education level, political preferences, and/orother classifications.

In some embodiments, the DPO may query, e.g., 1407, a database for awidget template (e.g., javascript, AJAX lightbox, etc.) using the userdevice attributes, user location, user location type, and userdemographic(s) as key terms in the query. Thus, in some embodiments, theDPO may be able to generate, using a template widget, a customizedwidget that is optimized based on the user device attributes, userlocation, user location type, and user demographic(s), among otherattributes. The DPO may identify, e.g., 1408, a merchant ID for themerchant, and query a database for merchant-specific customization(e.g., see skins in FIG. 4E). The DPO may generate a user-merchantsession specific widget using the obtained widget template (customizedto the user, user device, user location, etc.) and merchant-specificcustomizations, e.g., 1409. The DPO may return the user-merchantspecific widget to source of obtained trigger, e.g., 1410. In someembodiments, the DPO may provide a notification of customizations to beperformed for optimizing a user payment interface via an applicationprogramming interface (e.g., encoded in XML or JSON data format), asopposed to providing the customized interface itself.

FIGS. 15A-B show data flow diagrams illustrating an example purchasetransaction authorization procedure in some embodiments of the DPO. Withreference to FIG. 15A, in some embodiments, a user, e.g., 1501 a, maywish to utilize a virtual wallet account to purchase a product, service,offering, and/or the like (“product”), from a merchant via a merchantonline site or in the merchant's store. The user may utilize a physicalcard, or a user wallet device, e.g., 1501 b, to access the user'svirtual wallet account. For example, the user wallet device may be apersonal/laptop computer, cellular telephone, smartphone, tablet, eBookreader, netbook, gaming console, and/or the like. The user may provide awallet access input, e.g., 1511, into the user wallet device. In variousembodiments, the user input may include, but not be limited to: a singletap (e.g., a one-tap mobile app purchasing embodiment) of a touchscreeninterface, keyboard entry, card swipe, activating a RFID/NFC enabledhardware device (e.g., electronic card having multiple accounts,smartphone, tablet, etc.) within the user device, mouse clicks,depressing buttons on a joystick/game console, voice commands,single/multi-touch gestures on a touch-sensitive interface, touchinguser interface elements on a touch-sensitive display, and/or the like.In some embodiments, the user wallet device may authenticate the userbased on the user's wallet access input, and provide virtual walletfeatures for the user.

In some embodiments, upon authenticating the user for access to virtualwallet features, the user wallet device may provide a transactionauthorization input, e.g., 1514, to a point-of-sale (“PoS”) client,e.g., 1502. For example, the user wallet device may communicate with thePoS client via Bluetooth, Wi-Fi, cellular communication, one- or two-waynear-field communication (“NFC”), and/or the like. In embodiments wherethe user utilizes a plastic card instead of the user wallet device, theuser may swipe the plastic card at the PoS client to transferinformation from the plastic card into the PoS client. For example, thePoS client may obtain, as transaction authorization input 1514, track 1data from the user's plastic card (e.g., credit card, debit card,prepaid card, charge card, etc.), such as the example track 1 dataprovided below:

%B123456789012345{circumflex over ( )}PUBLIC/J.Q.{circumflex over( )}99011200000000000000**901*** ***?* (wherein ‘123456789012345’ is thecard number of ‘J.Q. Public’ and has a CVV number of 901. ‘990112’ is aservice code, and *** represents decimal digits which change randomlyeach time the card is used.)

In embodiments where the user utilizes a user wallet device, the userwallet device may provide payment information to the PoS client,formatted according to a data formatting protocol appropriate to thecommunication mechanism employed in the communication between the userwallet device and the PoS client. An example listing of transactionauthorization input 1514, substantially in the form of XML-formatteddata, is provided below:

<?XML version = “1.0” encoding = “UTF-8”?><transaction_authorization_input>   <payment_data>      <account>        <charge_priority>1</charge_priority>        <charge_ratio>40%</charge_ratio>        <account_number>123456789012345         </account_number>        <account_name>John Q. Public</account_name>        <bill_add>987 Green St #456, Chicago, IL 94652        </bill_add>         <ship_add>987 Green St #456, Chicago, IL94652         </ship_add>         <CVV>123</CVV>      </account>     <account>         <charge_priority>1</charge_priority>        <charge_ratio>60%</charge_ratio>        <account_number>234567890123456         </account_number>        <account_name>John Q. Public</account_name>        <bill_add>987 Green St #456, Chicago, IL 94652        </bill_add>         <ship_add>987 Green St #456, Chicago, IL94652         </ship_add>         <CVV>173</CVV>      </account>     <account>         <charge_priority>2</charge_priority>        <charge_ratio>100%</charge_ratio>        <account_number>345678901234567         </account_number>        <account_name>John Q. Public</account_name>        <bill_add>987 Green St #456, Chicago, IL 94652        </bill_add>         <ship_add>987 Green St #456, Chicago, IL94652         </ship_add>         <CVV>695</CVV>      </account>  </payment_data>   <!--optional data-->   <timestamp>2011-02-2215:22:43</timestamp>   <expiry_lapse>00:00:30</expiry_lapse>  <secure_key>0445329070598623487956543322</secure_key>  <alerts_track_flag>TRUE</alerts_track_flag>   <wallet_device_details>     <device_IP>192.168.23.126</client_IP>     <device_type>smartphone</client_type>      <device_model>HTCHero</client_model>      <OS>Android 2.2</OS>     <wallet_app_installed_flag>true      </wallet_app_installed_flag>  </wallet_device_details> </transaction_authorization_input>

In some embodiments, the PoS client may generate a card authorizationrequest, e.g., 1515, using the obtained transaction authorization inputfrom the user wallet device, and/or product/checkout data (see, e.g.,FIG. 9, 915-917). An example listing of a card authorization request1515, substantially in the form of a HTTP(S) POST message includingXML-formatted data, is provided below:

POST /authorizationrequests.php HTTP/1.1 Host: www.acquirer.comContent-Type: Application/XML Content-Length: 1306 <?XML version = “1.0”encoding = “UTF-8”?> <card_authorization_request>  <session_ID>4NFU4RG94</order_ID>   <timestamp>2011-02-2215:22:43</timestamp>   <expiry>00:00:30</expiry>  <alerts_URL>www.merchant.com/shopcarts.php?sessionID=  AEBB4356</alerts_URL>   <!--optional data-->  <user_ID>john.q.public@gmail.com</user_ID>   <PoS_details>    <PoS_IP>192.168.23.126</client_IP>    <PoS_type>smartphone</client_type>     <PoS_model>HTCHero</client_model>     <OS>Android 2.2</OS>    <app_installed_flag>true</app_installed_flag>   </PoS_details>  <purchase_details>     <num_products>1</num_products>     <product>      <product_type>book</product_type>       <product_params>        <product_title>XML for dummies</product_title>        <ISBN>938-2-14-168710-0</ISBN>         <edition>2nded.</edition>         <cover>hardbound</cover>        <seller>bestbuybooks</seller>       </product_params>      <quantity>1</quantity>     </product>   </purchase_details>  <merchant_params>     <merchant_id>3FBCR4INC</merchant_id>    <merchant_name>Books & Things, Inc.</merchant_name>    <merchant_auth_key>1NNF484MCP59CHB27365     </merchant_auth_key>  </merchant_params>   <account_params>     <account_name>John Q.Public</account_name>     <account_type>credit</account_type>    <account_num>123456789012345</account_num>     <billing_address>123Green St., Norman, OK 98765     </billing_address>    <phone>123-456-7809</phone>     <sign>/jqp/</sign>    <confirm_type>email</confirm_type>    <contact_info>john.q.public@gmail.com</contact_info>  </account_params>   <shipping_info>     <shipping_adress>same asbilling</shipping_address>     <ship_type>expedited</ship_type>    <ship_carrier>FedEx</ship_carrier>    <ship_account>123-45-678</ship_account>    <tracking_flag>true</tracking_flag>     <sign_flag>false</sign_flag>  </shipping_info> </card_authorization_request>

In some implementations, the card authorization request generated by thePoS client may include a minimum of information required to process thepurchase transaction. For example, this may improve the efficiency ofcommunicating the purchase transaction request, and may alsoadvantageously improve the privacy protections provided to the userand/or merchant. For example, in some implementations, the cardauthorization request may include at least a session ID for the user'sshopping session with the merchant. The session ID may be utilized byany component and/or entity having the appropriate access authority toaccess a secure site on the merchant server to obtain alerts, reminders,and/or other data about the transaction(s) within that shopping sessionbetween the user and the merchant. In some embodiments, the PoS clientmay provide the generated card authorization request to the merchantserver, e.g., 1516. The merchant server may forward the cardauthorization request to a MaaS server, e.g., 1504 a, for routing thecard authorization request to the appropriate payment network forpayment processing. For example, the MaaS server may be able to selectfrom payment networks, such as Visa, Mastercard, American Express,Paypal, etc., to process various types of transactions including, butnot limited to: credit card, debit card, prepaid card, B2B and/or liketransactions. In some embodiments, the merchant server may query adatabase, e.g., merchant/acquirer database 1503 b, for a network addressof the payment gateway server, for example by using a portion of a userpayment card number, or a user ID (such as an email address) as akeyword for the database query. For example, the merchant server mayissue PHP/SQL commands to query a database table (such as FIG. 23, PayGateways 2319 h) for a URL of the MaaS server. An example paymentgateway address query 1517, substantially in the form of PHP/SQLcommands, is provided below:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.93.179.112”,$DBserver,$password); // access databaseserver mysql_select_db(“DPO_DB.SQL”); // select database table to search//create query $query = “SELECT paygate_id paygate_address paygate_URLpaygate_name FROM  PayGatewayTable WHERE card_num LIKE ‘%’ $cardnum”;$result = mysql_query($query); // perform the search querymysql_close(“DPO_DB.SQL”); // close database access ?>

In response, the merchant/acquirer database may provide the requestedpayment gateway address, e.g., 1518. The merchant server may forward thecard authorization request to the MaaS server using the providedaddress. In some embodiments, upon receiving the card authorizationrequest from the merchant server, the MaaS server may invoke a componentto provide one or more service associated with purchase transactionauthorization. For example, the MaaS server may invoke components forfraud prevention (see e.g., FIG. 2, risk management 206 b; VerifyChat,FIG. 3E), loyalty and/or rewards, and/or other services for which theuser-merchant combination is authorized. The MaaS server may forward thecard authorization request to a pay network server, e.g., 1935 a, forpayment processing. For example, the MaaS server may be able to selectfrom payment networks, such as Visa, Mastercard, American Express,Paypal, etc., to process various types of transactions including, butnot limited to: credit card, debit card, prepaid card, B2B and/or liketransactions. In some embodiments, the MaaS server may query a database,e.g., MaaS database 1504 b, for a network address of the payment networkserver, for example by using a portion of a user payment card number, ora user ID (such as an email address) as a keyword for the databasequery. For example, the MaaS server may issue PHP/SQL commands to querya database table (such as FIG. 23, Pay Gateways 2319 h) for a URL of thepay network server. An example payment network address query 1521,substantially in the form of PHP/SQL commands, is provided below:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.93.179.112”,$DBserver,$password); // access databaseserver mysql_select_db(“DPO_DB.SQL”); // select database table to search//create query $query = “SELECT payNET_id payNET_address payNET_URLpayNET_name FROM  PayGatewayTable WHERE card_num LIKE ‘%’ $cardnum”;$result = mysql_query($query); // perform the search querymysql_close(“DPO_DB.SQL”); // close database access ?>

In response, the payment gateway database may provide the requestedpayment network address, e.g., 1522. The MaaS server may forward thecard authorization request to the pay network server using the providedaddress, e.g., 1523.

With reference to FIG. 15B, in some embodiments, the pay network servermay process the transaction so as to transfer funds for the purchaseinto an account stored on an acquirer of the merchant. For example, theacquirer may be a financial institution maintaining an account of themerchant. For example, the proceeds of transactions processed by themerchant may be deposited into an account maintained by at a server ofthe acquirer.

In some embodiments, the pay network server may generate a query, e.g.,1524, for issuer server(s) corresponding to the user-selected paymentoptions. For example, the user's account may be linked to one or moreissuer financial institutions (“issuers”), such as banking institutions,which issued the account(s) for the user. For example, such accounts mayinclude, but not be limited to: credit card, debit card, prepaid card,checking, savings, money market, certificates of deposit, stored (cash)value accounts and/or the like. Issuer server(s), e.g., 1506 a, of theissuer(s) may maintain details of the user's account(s). In someembodiments, a database, e.g., pay network database 1505 b, may storedetails of the issuer server(s) associated with the issuer(s). In someembodiments, the pay network server may query a database, e.g., paynetwork database 1505 b, for a network address of the issuer(s)server(s), for example by using a portion of a user payment card number,or a user ID (such as an email address) as a keyword for the databasequery. For example, the merchant server may issue PHP/SQL commands toquery a database table (such as FIG. 23, Issuers 2319 f) for networkaddress(es) of the issuer(s) server(s). An example issuer serveraddress(es) query 1524, substantially in the form of PHP/SQL commands,is provided below:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.93.179.112”,$DBserver,$password); // access databaseserver mysql_select_db(“DPO_DB.SQL”); // select database table to search//create query $query = “SELECT issuer_id issuer_address issuer_URLissuer_name FROM  IssuersTable WHERE card_num LIKE ‘%’ $cardnum”;$result = mysql_query($query); // perform the search querymysql_close(“DPO_DB.SQL”); // close database access ?>

In response to obtaining the issuer server query, e.g., 1524, the paynetwork database may provide, e.g., 1525, the requested issuer serverdata to the pay network server. In some embodiments, the pay networkserver may utilize the issuer server data to generate fundsauthorization request(s), e.g., 1526, for each of the issuer server(s)selected based on the pre-defined payment settings associated with theuser's virtual wallet, and/or the user's payment options input, andprovide the funds authorization request(s) to the issuer server(s). Insome embodiments, the funds authorization request(s) may include detailssuch as, but not limited to: the costs to the user involved in thetransaction, card account details of the user, user billing and/orshipping information, and/or the like. An example listing of a fundsauthorization request 1526, substantially in the form of a HTTP(S) POSTmessage including XML-formatted data, is provided below:

POST /fundsauthorizationrequest.php HTTP/1.1 Host: www.issuer.comContent-Type: Application/XML Content-Length: 624 <?XML version = “1.0”encoding = “UTF-8”?> <funds_authorization_request>  <query_ID>VNEI39FK</query_ID>   <timestamp>2011-02-2215:22:44</timestamp>   <transaction_cost>$22.61</transaction_cost>  <account_params>     <account_type>checking</account_type>    <account_num>1234567890123456</account_num>   </account_params>  <!--optional parameters-->   <purchase_summary>    <num_products>1</num_products>     <product>      <product_summary>Book - XML for dummies       </product_summary>      <product_quantity>1</product_quantity?     </product>  </purchase_summary>   <merchant_params>    <merchant_id>3FBCR4INC</merchant_id>     <merchant_name>Books &Things, Inc.</merchant_name>     <merchant_auth_key>1NNF484MCP59CHB27365    </merchant_auth_key>   </merchant_params></funds_authorization_request>

In some embodiments, an issuer server may parse the authorizationrequest(s), and based on the request details may query a database, e.g.,user profile database 1506 b, for data associated with an account linkedto the user. For example, the merchant server may issue PHP/SQL commandsto query a database table (such as FIG. 23, Accounts 2319 d) for useraccount(s) data. An example user account(s) query 1527, substantially inthe form of PHP/SQL commands, is provided below:

<?PHP <?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.93.179.112”,$DBserver,$password); // access databaseserver mysql_select_db(“DPO_DB.SQL”); // select database table to search//create query $query = “SELECT issuer user_id user_name user_balanceaccount_type FROM  AccountsTable WHERE account_num LIKE ‘%’$accountnum”; $result = mysql_query($query); // perform the search querymysql_close(“DPO_DB.SQL”); // close database access ?>

In some embodiments, on obtaining the user account(s) data, e.g., 1528,the issuer server may determine whether the user can pay for thetransaction using funds available in the account, 1529. For example, theissuer server may determine whether the user has a sufficient balanceremaining in the account, sufficient credit associated with the account,and/or the like. Based on the determination, the issuer server(s) mayprovide a funds authorization response, e.g., 1530, to the pay networkserver. For example, the issuer server(s) may provide a HTTP(S) POSTmessage similar to the examples above. In some embodiments, if at leastone issuer server determines that the user cannot pay for thetransaction using the funds available in the account, the pay networkserver may request payment options again from the user (e.g., byproviding an authorization fail message to the user device andrequesting the user device to provide new payment options), andre-attempt authorization for the purchase transaction. In someembodiments, if the number of failed authorization attempts exceeds athreshold, the pay network server may abort the authorization process,and provide an “authorization fail” message to the merchant server, userdevice and/or client.

In some embodiments, the pay network server may obtain the fundsauthorization response including a notification of successfulauthorization, and parse the message to extract authorization details.Upon determining that the user possesses sufficient funds for thetransaction, the pay network server may invoke a component to providevalue-add services for the user, e.g., 1531. For example, the paynetwork server may invoke a P2P social network marketing component topost a notification of the user's successful purchase of the product toa social profile of the user hosted by a social networking service. Asanother example, the pay network server may invoke the P2P socialnetwork marketing component to reward a different user whose social postvia a social networking service caused the user to engage in thepurchase transaction. For example, the pay network server may invoke theexample P2P social network marketing component discussed below withreference to FIGS. 17-18. In some embodiments, the pay network servermay also generate a transaction data record from the authorizationrequest and/or authorization response, and store the details of thetransaction and authorization relating to the transaction in atransactions database. For example, the pay network server may issuePHP/SQL commands to store the data to a database table (such as FIG. 23,Transactions 2319 i). An example transaction store command,substantially in the form of PHP/SQL commands, is provided below:

<?PHP header(‘Content-Type: text/plain’);mysql_connect(“254.92.185.103”,$DBserver,$password); // access databaseserver mysql_select(“DPO_DB.SQL”); // select database to appendmysql_query(“INSERT INTO TransactionsTable (PurchasesTable (timestamp,  purchase_summary_list, num_products, product_summary,product_quantity,   transaction_cost, account_params_list, account_name,account_type,   account_num, billing_addres, zipcode, phone, sign,merchant_params_list,   merchant_id, merchant_name, merchant_auth_key)VALUES (time( ), $purchase_summary_list, $num_products,$product_summary,   $product_quantity, $transaction_cost,$account_params_list, $account_name,   $account_type, $account_num,$billing_addres, $zipcode, $phone, $sign,   $merchant_params_list,$merchant_id, $merchant_name, $merchant_auth_key)”);   // add data totable in database mysql_close(“DPO_DB.SQL”); // close connection todatabase ?>

In some embodiments, the pay network server may forward a transactionauthorization response, e.g., 1532, to the user wallet device, PoSclient, and/or merchant server. The merchant may obtain the transactionauthorization response, and determine from it that the user possessessufficient funds in the card account to conduct the transaction. Themerchant server may add a record of the transaction for the user to abatch of transaction data relating to authorized transactions. Forexample, the merchant may append the XML data pertaining to the usertransaction to an XML data file comprising XML data for transactionsthat have been authorized for various users, e.g., 1533, and store theXML data file, e.g., 1534, in a database, e.g., merchant database 404.For example, a batch XML data file may be structured similar to theexample XML data structure template provided below:

<?XML version = “1.0” encoding = “UTF-8”?> <merchant_data>  <merchant_id>3FBCR4INC</merchant_id>   <merchant_name>Books & Things,Inc.</merchant_name>   <merchant_auth_key>1NNF484MCP59CHB27365  </merchant_auth_key>   <account_number>123456789</account_number></merchant_data> <transaction_data>   <transaction 1>     ...  </transaction 1>   <transaction 2>     ...   </transaction 2>     .    .     .   <transaction n>     ...   </transaction n></transaction_data>

In some embodiments, the server may also generate a purchase receipt,e.g., 1533, and provide the purchase receipt to the client, e.g., 1535.The client may render and display, e.g., 1536, the purchase receipt forthe user. In some embodiments, the user's wallet device may also providea notification of successful authorization to the user. For example, thePoS client/user device may render a webpage, electronic message,text/SMS message, buffer a voicemail, emit a ring tone, and/or play anaudio message, etc., and provide output including, but not limited to:sounds, music, audio, video, images, tactile feedback, vibration alerts(e.g., on vibration-capable client devices such as a smartphone etc.),and/or the like.

FIGS. 16A-B show logic flow diagrams illustrating example aspects ofpurchase transaction authorization in some embodiments of the DPO, e.g.,a Purchase Transaction Authorization (“PTA”) component 1600. Withreference to FIG. 16A, in some embodiments, a user may wish to utilize avirtual wallet account to purchase a product, service, offering, and/orthe like (“product”), from a merchant via a merchant online site or inthe merchant's store. The user may utilize a physical card, or a userwallet device to access the user's virtual wallet account. For example,the user wallet device may be a personal/laptop computer, cellulartelephone, smartphone, tablet, eBook reader, netbook, gaming console,and/or the like. The user may provide a wallet access input, e.g., 1601,into the user wallet device. In various embodiments, the user input mayinclude, but not be limited to: a single tap (e.g., a one-tap mobile apppurchasing embodiment) of a touchscreen interface, keyboard entry, cardswipe, activating a RFID/NFC enabled hardware device (e.g., electroniccard having multiple accounts, smartphone, tablet, etc.) within the userdevice, mouse clicks, depressing buttons on a joystick/game console,voice commands, single/multi-touch gestures on a touch-sensitiveinterface, touching user interface elements on a touch-sensitivedisplay, and/or the like. In some embodiments, the user wallet devicemay authenticate the user based on the user's wallet access input, andprovide virtual wallet features for the user, e.g., 1602-1603.

In some embodiments, upon authenticating the user for access to virtualwallet features, the user wallet device may provide a transactionauthorization input, e.g., 1604, to a point-of-sale (“PoS”) client. Forexample, the user wallet device may communicate with the PoS client viaBluetooth, Wi-Fi, cellular communication, one- or two-way near-fieldcommunication (“NFC”), and/or the like. In embodiments where the userutilizes a plastic card instead of the user wallet device, the user mayswipe the plastic card at the PoS client to transfer information fromthe plastic card into the PoS client. In embodiments where the userutilizes a user wallet device, the user wallet device may providepayment information to the PoS client, formatted according to a dataformatting protocol appropriate to the communication mechanism employedin the communication between the user wallet device and the PoS client.

In some embodiments, the PoS client may obtain the transactionauthorization input, and parse the input to extract payment informationfrom the transaction authorization input, e.g., 1605. For example, thePoS client may utilize a parser, such as the example parsers providedbelow in the discussion with reference to FIG. 23. The PoS client maygenerate a card authorization request, e.g., 1606, using the obtainedtransaction authorization input from the user wallet device, and/orproduct/checkout data (see, e.g., FIG. 9, 915-917).

In some embodiments, the PoS client may provide the generated cardauthorization request to the merchant server. The merchant server mayforward the card authorization request to a MaaS server, for routing thecard authorization request to the appropriate payment network forpayment processing. For example, the MaaS server may be able to selectfrom payment networks, such as Visa, Mastercard, American Express,Paypal, etc., to process various types of transactions including, butnot limited to: credit card, debit card, prepaid card, B2B and/or liketransactions. In some embodiments, the merchant server may query adatabase, e.g., 1608, for a network address of the payment gatewayserver, for example by using a portion of a user payment card number, ora user ID (such as an email address) as a keyword for the databasequery. In response, the merchant/acquirer database may provide therequested payment gateway address, e.g., 1610. The merchant server mayforward the card authorization request to the MaaS server using theprovided address. In some embodiments, upon receiving the cardauthorization request from the merchant server, the MaaS server mayinvoke a component to provide one or more service associated withpurchase transaction authorization. For example, the MaaS server mayinvoke components for fraud prevention (see e.g., FIG. 2, riskmanagement 206 b; VerifyChat, FIG. 3E), loyalty and/or rewards, and/orother services for which the user-merchant combination is authorized.The MaaS server may forward the card authorization request to a paynetwork server for payment processing, e.g., 1614. For example, the MaaSserver may be able to select from payment networks, such as Visa,Mastercard, American Express, Paypal, etc., to process various types oftransactions including, but not limited to: credit card, debit card,prepaid card, B2B and/or like transactions. In some embodiments, theMaaS server may query a database, e.g., 1612, for a network address ofthe payment network server, for example by using a portion of a userpayment card number, or a user ID (such as an email address) as akeyword for the database query. In response, the payment gatewaydatabase may provide the requested payment network address, e.g., 1613.The MaaS server may forward the card authorization request to the paynetwork server using the provided address, e.g., 1614.

With reference to FIG. 16B, in some embodiments, the pay network servermay process the transaction so as to transfer funds for the purchaseinto an account stored on an acquirer of the merchant. For example, theacquirer may be a financial institution maintaining an account of themerchant. For example, the proceeds of transactions processed by themerchant may be deposited into an account maintained by at a server ofthe acquirer. In some embodiments, the pay network server may generate aquery, e.g., 1615, for issuer server(s) corresponding to theuser-selected payment options. For example, the user's account may belinked to one or more issuer financial institutions (“issuers”), such asbanking institutions, which issued the account(s) for the user. Forexample, such accounts may include, but not be limited to: credit card,debit card, prepaid card, checking, savings, money market, certificatesof deposit, stored (cash) value accounts and/or the like. Issuerserver(s) of the issuer(s) may maintain details of the user'saccount(s). In some embodiments, a database, e.g., a pay networkdatabase, may store details of the issuer server(s) associated with theissuer(s). In some embodiments, the pay network server may query adatabase, e.g., 1615, for a network address of the issuer(s) server(s),for example by using a portion of a user payment card number, or a userID (such as an email address) as a keyword for the database query.

In response to obtaining the issuer server query, the pay networkdatabase may provide, e.g., 1616, the requested issuer server data tothe pay network server. In some embodiments, the pay network server mayutilize the issuer server data to generate funds authorizationrequest(s), e.g., 1617, for each of the issuer server(s) selected basedon the pre-defined payment settings associated with the user's virtualwallet, and/or the user's payment options input, and provide the fundsauthorization request(s) to the issuer server(s). In some embodiments,the funds authorization request(s) may include details such as, but notlimited to: the costs to the user involved in the transaction, cardaccount details of the user, user billing and/or shipping information,and/or the like. In some embodiments, an issuer server may parse theauthorization request(s), e.g., 1618, and based on the request detailsmay query a database, e.g., 1619, for data associated with an accountlinked to the user.

In some embodiments, on obtaining the user account(s) data, e.g., 1620,the issuer server may determine whether the user can pay for thetransaction using funds available in the account, e.g., 1621. Forexample, the issuer server may determine whether the user has asufficient balance remaining in the account, sufficient creditassociated with the account, and/or the like. Based on thedetermination, the issuer server(s) may provide a funds authorizationresponse, e.g., 1622, to the pay network server. In some embodiments, ifat least one issuer server determines that the user cannot pay for thetransaction using the funds available in the account, the pay networkserver may request payment options again from the user (e.g., byproviding an authorization fail message to the user device andrequesting the user device to provide new payment options), andre-attempt authorization for the purchase transaction. In someembodiments, if the number of failed authorization attempts exceeds athreshold, the pay network server may abort the authorization process,and provide an “authorization fail” message to the merchant server, userdevice and/or client.

In some embodiments, the pay network server may obtain the fundsauthorization response including a notification of successfulauthorization, and parse the message to extract authorization details.Upon determining that the user possesses sufficient funds for thetransaction, e.g., 1623, the pay network server may invoke a componentto provide value-add services for the user, e.g., 1623. For example, thepay network server may invoke a P2P social network marketing componentto post a notification of the user's successful purchase of the productto a social profile of the user hosted by a social networking service.As another example, the pay network server may invoke the P2P socialnetwork marketing component to reward a different user whose social postvia a social networking service caused the user to engage in thepurchase transaction. For example, the pay network server may invoke theexample P2P social network marketing component discussed below withreference to FIGS. 17-18.

In some embodiments, the pay network server may forward a transactionauthorization response to the user wallet device, PoS client, and/ormerchant server. The merchant may parse, e.g., 1624, the transactionauthorization response, and determine from it that the user possessessufficient funds in the card account to conduct the transaction, e.g.,1625, option“Yes.” The merchant server may add a record of thetransaction for the user to a batch of transaction data relating toauthorized transactions. For example, the merchant may append the XMLdata pertaining to the user transaction to an XML data file comprisingXML data for transactions that have been authorized for various users,e.g., 1626, and store the XML data file, e.g., 1627, in a database. Insome embodiments, the server may also generate a purchase receipt, e.g.,1628, and provide the purchase receipt to the client. The client mayrender and display, e.g., 1629, the purchase receipt for the user. Insome embodiments, the user's wallet device may also provide anotification of successful authorization to the user. For example, thePoS client/user device may render a webpage, electronic message,text/SMS message, buffer a voicemail, emit a ring tone, and/or play anaudio message, etc., and provide output including, but not limited to:sounds, music, audio, video, images, tactile feedback, vibration alerts(e.g., on vibration-capable client devices such as a smartphone etc.),and/or the like.

FIGS. 17A-D show block and data flow diagrams illustrating an exampleperson-2-person social network marketing procedure in some embodimentsof the DPO. In some embodiments, the DPO may facilitate rewardingindividual users of a social network for any sales activity that mightarise from them posting, commenting or communicating with their friendson a social network on their personal purchasing activities, preferencesor tastes. For example, in some embodiments, the DPO may implement anAffiliate Tracking Server (referred to as Server) that may keep track ofuser's communications (posts, comments, update and the like) on a socialnetwork through integration to the social network server, API orplatform. When a user updates his/her social network communications witha product or service that he/she bought or recommends, the AffiliateServer may track the update, and its associated vendor, advertiser orproduct link in the communication. The Affiliate Server may also trackany user in the friend's network that clicks on that link. If any memberfrom the social network who received or viewed the communication or fromthe users “social graph”) clicks on the link and lands on the vendor,advertiser or product site, the Affiliate Server may credit theclick-through to the user who created the original communication post.The Affiliate Server may, in some embodiments, place tracking pixels onthe advertisers/brand/vendor site. The tracking pixel may send furtherdetails if the referred user did any purchase activity or browsingactivity. The Affiliate Server may then attribute the credit related tothe browsing of the site (click) or of the purchase (action) done by thereferred user to the recommending user's (affiliate user's) account.

Thus, in some embodiments, there may be no need for the recommendinguser profile information to get communicated to the vendor by theAffiliate Server, thus ensuring the privacy of both the recommendinguser and the referred user. The “Affiliate Server” Rewards module mayreward the recommending user on the successful click or action (sale) tothe second user (referred user) resulting from the recommending userpropagating the vendor offering to the second user, through his/herSocial Network communication. The reward may include one or more itemsselected from a group including a cash value, one or more virtualcurrency based rewards, or products, offers or coupons. A description ofa user interacting with the invention in an example scenario follows: AFacebook user joins the P2P Affiliate program and in so doing grants theAffiliate Server access to the users profile or social graph data. Thisaccess could be granted in the form of adding a Facebook AffiliateApplication, or through the use of Facebook Connect on a website. Theuser is now incented to post to his/her social network about anyproducts he/she finds appealing, or can endorse because such posts cannot only infoml his/her friends about his/her preferences, but can alsolead to affiliate rewards if his/her friends decide to click on theposts. The user posts a link that he/she recently purchased a pair ofLevy Jeans. This post gets communicated to hundreds of the user'sfriends through Facebook's friend feed. Ten users click on the link tobrowse the Levy Jean's Website. Two of the then users make a jeanspurchase of $50 each. Levy has agreed to reward an affiliate with $0.50for every user who browses their site and 5% of the sales price for anypurchase. The Affiliate Server tracks the activity of the referred userson Levy's site and knows to reward the recommending user appropriatelywith $6.00 in this example. The Affiliate Server may take a percentageof all rewards as a service fee, or may receive a service fee from themerchants independently.

With reference to FIG. 17C, in some embodiments, a MaaS server or otherentity or component within the DPO may obtain a trigger, e.g., 1711, toprovide P2P social network marketing service (see, e.g., FIG. 15B,1531). In some embodiments, the MaaS server may parse the obtainedtrigger for provide P2P social network marketing service, and extracttransaction details from the trigger, e.g., 1714. For example, the paynetwork may extract fields such as, but not limited to: session ID,timestamp, alters URL, user ID, PoS client type and address, purchasedproducts, product pricing, offers redeemed in the purchase, couponsutilized in the purchase, rewards provided due to the purchase, merchantname, URL to the product on the merchant website, and/or the like. Insome embodiments, the MaaS server may generate a user social postrequest for a social networking service using the details of thepurchase transactions extracted from the trigger and/or othercommunications (e.g., card authorization requests) associated with thetrigger. For example, the MaaS server may query, e.g., 1712-1713, itsown database (e.g., via PHP/SQL commands) to obtain a user ID of theuser associated with the social networking service. Using the obtaineduser profile data 1713 from the MaaS database 1704 b, the MaaS servermay generate a user social post request, e.g., an API call, to thesocial networking server 1705 a. For example, the MaaS server mayutilize a HTTP(S) POST request message similar to the examples providedpreviously. As another example, the MaaS server may utilize an APIprovided by the social networking service. For example, the MaaS servermay execute a PHP script to make a call to the social networkingservice's API. An example listing for a user social post request 1715,substantially in the form of PHP commands, is provided below:

<?PHP header(‘Content-Type: text/plain’); $attachment = array(‘message’=> ‘John just got a great deal at Merchant!...’,  ‘name’ => $title, ‘link’ => ‘http://merchant.com/’ . $urlTitle,  ‘description’ =>‘Review: ’ . $review,  ‘picture’ => $picLocal  );  if(!($sendMessage =$facebook->api(‘/me/feed/’,‘post’,$attachment))){  $errors=error_get_last( );  echo “Facebook publish error: ”.$errors[‘type’]; echo “<br />\n”.$errors[‘message’];  } ?>

In some embodiments, the social networking service may generate a userprofile social post command, e.g., 1716, in response to obtaining theuser social post request from the MaaS server. The social network servermay provide a social post confirmation, e.g., 1717, in response, to theMaaS server.

With reference to FIG. 17D, in some embodiments, the MaaS server mayattempt to identify the source of the recommendation leading to theproduct purchase by the user. For example, the MaaS server may parse allof the communications it received with regard to the purchasetransaction (e.g., flexible monetization service requests, cardauthorization requests and/or the like) to identify a source for therecommendations. In some embodiments, the MaaS server may identify asocial post of another user, e.g., user 2 1701 a, as being part of thesocial search results that were presented to the user, which caused theuser to engage in the purchase transaction (for example, the userperforming the purchase transactions may have been in a similarsituation to the user 701 in FIG. 7, and obtained a recommendation fromuser 2 1701 a as part of the purchase catalog browsing display). Forexample, the MaaS server may determine whether a recommendation was froma social search result. The MaaS server may identify a user 2 associatedwith the social search result (e.g., a user 2 who posted therecommendation to the social network; a user on whose behalf the MaaSserver generated a social post request, etc.), e.g., 1720. The MaaSserver may determine a reward to provide for the user 2. For example,the reward may include a crediting of real currency, virtual currency,an additional of rewards points, loyalty points, providing additionaloffers, recommendations, providing additional posts to the socialprofile of the user 2 on other related offers and/or products that user2 may be interested in purchasing, and/or other benefits for the user 2.In some embodiments, the MaaS server may provide the social marketingcredit request to an issuer server hosting an account of the user 2,e.g., 1722. The issuer server may, in response, generate a user accountcredit command, e.g., 1723, to the issuer database, e.g., 1706 b. Insome embodiments, the issuer server may also provide a social marketingcredit notification, e.g., 1724, to a device of the user 2, e.g., 1701b, which may display, e.g., 1725, the credit notification to the user 2.

FIGS. 18A-B shows logic flow diagrams illustrating example aspects ofperson-2-person social network marketing in some embodiments of the DPO,e.g., a Person-2-Person (P2P) Social Network Marketing (“P2P-SNM”)component 1800. In some embodiments, a MaaS server or other entity orcomponent within the DPO may obtain a trigger, e.g., 1801, to provideP2P social network marketing service (see, e.g., a FIG. 15B, 1531). Insome embodiments, the MaaS server may parse the obtained trigger forprovide P2P social network marketing service, and extract transactiondetails from the trigger. For example, the pay network may extractfields such as, but not limited to: session ID, timestamp, alters URL,user ID, PoS client type and address, purchased products, productpricing, offers redeemed in the purchase, coupons utilized in thepurchase, rewards provided due to the purchase, merchant name, URL tothe product on the merchant website, and/or the like. In someembodiments, the MaaS server may generate a user social post request fora social networking service using the details of the purchasetransactions extracted from the trigger and/or other communications(e.g., card authorization requests) associated with the trigger. Forexample, the MaaS server may query, e.g., 1802-1803, its own database(e.g., via PHP/SQL commands) to obtain a user ID of the user associatedwith the social networking service. Using the obtained user profiledata, e.g., 1803, from the MaaS database, the MaaS server may generate auser social post request, e.g., an API call, to the social networkingserver 1805-1807. For example, the MaaS server may utilize a HTTP(S)POST request message similar to the examples provided previously. Asanother example, the MaaS server may utilize an API provided by thesocial networking service. In some embodiments, the social networkingservice may generate a user profile social post command, e.g., 1808, inresponse to obtaining the user social post request from the MaaS server.The social network server may provide a social post confirmation, e.g.,1810, in response, to the MaaS server.

With reference to FIG. 18B, in some embodiments, the MaaS server mayattempt to identify the source of the recommendation leading to theproduct purchase by the user. For example, the MaaS server may parse allof the communications it received with regard to the purchasetransaction (e.g., flexible monetization service requests, cardauthorization requests and/or the like) to identify a source for therecommendations. In some embodiments, the MaaS server may identify asocial post of another user, e.g., user 2, as being part of the socialsearch results that were presented to the user, which caused the user toengage in the purchase transaction (for example, the user performing thepurchase transactions may have been in a similar situation to the user701 in FIG. 7, and obtained a recommendation from user 2 1801 a as partof the purchase catalog browsing display). For example, the MaaS servermay determine, e.g., 1812, whether a recommendation was from a socialsearch result. The MaaS server may identify a user 2 associated with thesocial search result (e.g., a user 2 who posted the recommendation tothe social network; a user on whose behalf the MaaS server generated asocial post request, etc.), e.g., 1814. The MaaS server may determine areward to provide for the user 2. For example, the reward may include acrediting of real currency, virtual currency, an additional of rewardspoints, loyalty points, providing additional offers, recommendations,providing additional posts to the social profile of the user 2 on otherrelated offers and/or products that user 2 may be interested inpurchasing, and/or other benefits for the user 2. In some embodiments,the MaaS server may provide the social marketing credit request to anissuer server hosting an account of the user 2, e.g., 1815. The issuerserver may, in response, generate a user account credit command, e.g.,1817, to the issuer database. In some embodiments, the issuer server mayalso provide a social marketing credit notification, e.g., 1816, to adevice of the user 2, which may display, e.g., 1818, the creditnotification to the user 2.

FIGS. 19A-B show data flow diagrams illustrating an example purchasetransaction clearance procedure in some embodiments of the DPO. Withreference to FIG. 19A, in some embodiments, a merchant server, e.g.,1903 a, may initiate clearance of a batch of authorized transactions.For example, the merchant server may generate a batch data request,e.g., 1911, and provide the request, to a merchant database, e.g., 1903b. For example, the merchant server may utilize PHP/SQL commands similarto the examples provided above to query a relational database. Inresponse to the batch data request, the database may provide therequested batch data, e.g., 1912. The server may generate a batchclearance request, e.g., 1913, using the batch data obtained from thedatabase, and provide, e.g., 1914, the batch clearance request to anacquirer server, e.g., 1907 a. For example, the merchant server mayprovide a HTTP(S) POST message including XML-formatted batch data in themessage body for the acquirer server. The acquirer server may generate,e.g., 1915, a batch payment request using the obtained batch clearancerequest, and provide, e.g., 1918, the batch payment request to the paynetwork server, e.g., 1905 a. The pay network server may parse the batchpayment request, and extract the transaction data for each transactionstored in the batch payment request, e.g., 1919. The pay network servermay store the transaction data, e.g., 1920, for each transaction in adatabase, e.g., pay network database 1905 b. In some embodiments, thepay network server may invoke a component to provide analytics based onthe transactions of the merchant for whom purchase transaction are beingcleared. For example, the pay network server may invoke a geographictransaction volume analytics component, such as the example componentdiscussed below with reference to FIGS. 21-22. Thus, in someembodiments, the pay network server may provide analytics-basedvalue-added services for the merchant and/or the merchant's users.

With reference to FIG. 19B, in some embodiments, for each extractedtransaction, the pay network server may query, e.g., 1923, a database,e.g., pay network database 1905 b, for an address of an issuer server.For example, the pay network server may utilize PHP/SQL commands similarto the examples provided above. The pay network server may generate anindividual payment request, e.g., 1925, for each transaction for whichit has extracted transaction data, and provide the individual paymentrequest, e.g., 1925, to the issuer server, e.g., 1906 a. For example,the pay network server may provide an individual payment request to theissuer server(s) as a HTTP(S) POST message including XML-formatted data.An example listing of an individual payment request 1925, substantiallyin the form of a HTTP(S) POST message including XML-formatted data, isprovided below:

POST /paymentrequest.php HTTP/1.1 Host: www.issuer.com Content-Type:Application/XML Content-Length: 788 <?XML version = “1.0” encoding =“UTF-8”?> <pay_request>   <request_ID>CNI4ICNW2</request_ID>  <timestamp>2011-02-22 17:00:01</timestamp>  <pay_amount>$34.78</pay_amount>   <account_params>    <account_name>John Q. Public</account_name>    <account_type>credit</account_type>    <account_num>123456789012345</account_num>     <billing_address>123Green St., Norman, OK 98765     </billing_address>    <phone>123-456-7809</phone>     <sign>/jqp/</sign>  </account_params>   <merchant_params>    <merchant_id>3FBCR4INC</merchant_id>     <merchant_name>Books &Things, Inc.</merchant_name>     <merchant_auth_key>1NNF484MCP59CHB27365    </merchant_auth_key>   </merchant_params>   <purchase_summary>    <num_products>1</num_products>     <product>      <product_summary>Book - XML for dummies       </product_summary>      <product_quantity>1</product_quantity?     </product>  </purchase_summary> </pay_request>

In some embodiments, the issuer server may generate a payment command,e.g., 1927. For example, the issuer server may issue a command to deductfunds from the user's account (or add a charge to the user's credit cardaccount). The issuer server may issue a payment command, e.g., 1927, toa database storing the user's account information, e.g., user profiledatabase 1906 b. The issuer server may provide an individual paymentconfirmation, e.g., 1928, to the pay network server, which may forward,e.g., 1929, the funds transfer message to the acquirer server. Anexample listing of an individual payment confirmation 1928,substantially in the form of a HTTP(S) POST message includingXML-formatted data, is provided below:

POST /clearance.php HTTP/1.1 Host: www.acquirer.com Content-Type:Application/XML Content-Length: 206 <?XML version = “1.0” encoding =“UTF-8”?> <deposit_ack>   <request_ID>CNI4ICNW2</request_ID>  <clear_flag>true</clear_flag>   <timestamp>2011-02-2217:00:02</timestamp>   <deposit_amount>$34.78</deposit_amount></deposit_ack>

In some embodiments, the acquirer server may parse the individualpayment confirmation, and correlate the transaction (e.g., using therequest_ID field in the example above) to the merchant. The acquirerserver may then transfer the funds specified in the funds transfermessage to an account of the merchant. For example, the acquirer servermay query, e.g. 1930, an acquirer database 1907 b for payment ledgerand/or merchant account data, e.g., 1931. The acquirer server mayutilize payment ledger and/or merchant account data from the acquirerdatabase, along with the individual payment confirmation, to generateupdated payment ledger and/or merchant account data, e.g., 1932. Theacquirer server may then store, e.g., 1933, the updated payment ledgerand/or merchant account data to the acquire database.

FIGS. 20A-B show logic flow diagrams illustrating example aspects ofpurchase transaction clearance in some embodiments of the DPO, e.g., aPurchase Transaction Clearance (“PTC”) component 2000. With reference toFIG. 20A, in some embodiments, a merchant server may initiate clearanceof a batch of authorized transactions. For example, the merchant servermay generate a batch data request, e.g., 2001, and provide the requestto a merchant database. In response to the batch data request, thedatabase may provide the requested batch data, e.g., 2002. The servermay generate a batch clearance request, e.g., 2003, using the batch dataobtained from the database, and provide the batch clearance request toan acquirer server. The acquirer server may parse, e.g., 2004, theobtained batch clearance request, and generate, e.g., 2007, a batchpayment request using the obtained batch clearance request to provide,the batch payment request to a pay network server. For example, theacquirer server may query, e.g., 2005, an acquirer database for anaddress of a payment network server, and utilize the obtained address,e.g., 2006, to forward the generated batch payment request to the paynetwork server.

The pay network server may parse the batch payment request obtained fromthe acquirer server, and extract the transaction data for eachtransaction stored in the batch payment request, e.g., 2008. The paynetwork server may store the transaction data, e.g., 2009, for eachtransaction in a pay network database. In some embodiments, the paynetwork server may invoke a component, e.g., 2010, to provide analyticsbased on the transactions of the merchant for whom purchase transactionare being cleared. For example, the pay network server may invoke ageographic transaction volume analytics component, such as the examplecomponent discussed below with reference to FIGS. 21-22.

With reference to FIG. 20B, in some embodiments, for each extractedtransaction, the pay network server may query, e.g., 2011, a pay networkdatabase for an address of an issuer server. The pay network server maygenerate an individual payment request, e.g., 2013, for each transactionfor which it has extracted transaction data, and provide the individualpayment request to the issuer server. In some embodiments, the issuerserver may parse the individual payment request, e.g., 2014, andgenerate a payment command, e.g., 2015, based on the parsed individualpayment request. For example, the issuer server may issue a command todeduct funds from the user's account (or add a charge to the user'scredit card account). The issuer server may issue a payment command,e.g., 2015, to a database storing the user's account information, e.g.,a user profile database. The issuer server may provide an individualpayment confirmation, e.g., 2017, to the pay network server, which mayforward, e.g., 2018, the individual payment confirmation to the acquirerserver.

In some embodiments, the acquirer server may parse the individualpayment confirmation, and correlate the transaction (e.g., using therequest_ID field in the example above) to the merchant. The acquirerserver may then transfer the funds specified in the funds transfermessage to an account of the merchant. For example, the acquirer servermay query, e.g. 2019, an acquirer database for payment ledger and/ormerchant account data, e.g., 2020. The acquirer server may utilizepayment ledger and/or merchant account data from the acquirer database,along with the individual payment confirmation, to generate updatedpayment ledger and/or merchant account data, e.g., 2021. The acquirerserver may then store, e.g., 2022, the updated payment ledger and/ormerchant account data to the acquire database.

FIG. 21 shows a data flow diagram illustrating an example geographictransaction volume analytics procedure in some embodiments of the DPO.In some embodiments, a pay network server, e.g., 2105 a, or other entityor component within the DPO, may obtain a trigger to providetransaction-based analytics (see, e.g., FIG. 1519A, 1921). An examplelisting of a trigger 211, substantially in the form of a XML-formatteddata, is provided below:

<?XML version = “1.0” encoding = “UTF-8”?> <analytics_trigger>  <trigger_ID>FDSK9058543</trigger_ID>   <timestamp>2010-09-0122:22:22</timestamp>   <trigger_parameters>    <merchant_id>JTRE60594</merchant_id>     <report_type>heatmap</report_type>     <period>6mo</period>     <geo_filter>USonly</geo_filter>     <resolution>city</resolution>    <report_format>JPEG XLS</report_format>    <transaction_fi1ter>consumer</transaction_filter>    <PoS_filter>online</PoS_filter>     <pay_filter>creditcard</pay_filter>     <report_address>mailto:reports@merchant.com    </report_address>   </trigger_parameters> </analytics_trigger>

In some embodiments, the pay network server may parse the obtainedtrigger for transaction-based analytics, and extract a merchantidentifier from the trigger, e.g., 2112. For example, the pay networkmay extract a ‘merchant_id’ field from transaction data relating to atransaction involving the merchant, embedded in the obtained trigger.The pay network server may attempt to aggregate the transactions of themerchant to service the trigger. For example, the trigger may providefilters, e.g., an indication of the type of transaction, time period oftransaction, geographical region of transactions, and/or otherattributes to be utilized in the transaction-based analytics. The paynetwork server may utilize the filters provided in the trigger data toquery, e.g., 2113, a pay network database, e.g., 2105 b, fortransactions of the merchant. For example, the pay network server mayutilize PHP/SQL commands similar to those described previously to sendthe merchant transactions query 2113 to the pay network database. Inresponse, the pay network database may provide, e.g., 2114, the merchanttransactions data satisfying the filters provided by the triggerobtained by the pay network server. In some embodiments, the pay networkserver may analyze the aggregated transaction data to generate theanalytics. For example, based on the XML-encoded example triggerprovided above, the pay network server may engage in an algorithm toprovide a heat map of transactions in the US made by consumers usingcredit cards in an online environment, and provide a heat map, resolvedat the level of cities within the US in .JPEG image and .XLS spreadsheetformats to the email address reports@merchant.com. The pay networkserver may provide, e.g., 2116, the analytics results to the merchantacquirer server according to the instructions provided in the trigger,or using default settings if available. In some embodiments, themerchant/acquirer server may be able to display the analytics resultsvia a display system, and/or store, e.g., 2117, the analytics results toa merchant/acquirer database, e.g., 2103 b.

FIG. 22 shows a logic flow diagram illustrating example aspects ofgeographic transaction volume analytics in some embodiments of the DPO,e.g., a Geographic Transaction Volume Analytics (“GTVA”) component 2200.In some embodiments, a pay network server or other entity or componentwithin the DPO may obtain a trigger, e.g., 2201, to providetransaction-based analytics (see, e.g., FIG. 819A, 1921). In someembodiments, the pay network server may parse the obtained trigger fortransaction-based analytics, and extract a merchant identifier from thetrigger, e.g., 2202. For example, the pay network may extract a‘merchant_id’ field from transaction data relating to a transactioninvolving the merchant, embedded in the obtained trigger. The paynetwork server may attempt to aggregate the transactions of the merchantto service the trigger. For example, the trigger may provide filters,e.g., an indication of the type of transaction, time period oftransaction, geographical region of transactions, and/or otherattributes to be utilized in the transaction-based analytics. The paynetwork server may utilize the filters provided in the trigger data toquery, e.g., 2203, a pay network database for transactions of themerchant. In response, the pay network database may provide, e.g.,2203-2204, the merchant transactions data satisfying the filtersprovided by the trigger obtained by the pay network server. In someembodiments, the pay network server may analyze the aggregatedtransaction data to generate the analytics. For example, based on theXML-encoded example trigger provided above, the pay network server mayengage in an algorithm to provide a heat map of transactions in the USmade by consumers using credit cards in an online environment, andprovide a heat map, resolved at the level of cities within the US in.JPEG image and .XLS spreadsheet formats to the email addressreports@merchant.com. The pay network server may identify the parametersaccording to which to analyze the aggregated merchant transactions data,e.g., 2205. For example, the pay network server may select an identifiedparameters, e.g., 2206, and generate a histogram of the number oftransactions or transaction volume against all possible values of thatparameter, e.g., 2207. For example, if the parameter is “cities withinthe US,” then the pay network server may generate a histogram plottingthe number of transaction or total value of transaction against ay-axis, and a set of all cities within the US plotted against thex-axis. The pay network server may generate a graphical representationof the histogram, e.g., 2208. For example, if the identified parameteris a geographical parameter, then the pay network server may generate amap of the identified geographical region with a color scheme torepresent volume/total value of transactions by resolvable region. Asanother example, the pay network server may generate bar graphs, piecharts, and/or like graphical representations, regardless of the type ofparameter identified for analytics. In some embodiments, the pay networkserver may perform such histogram analysis, see e.g., 2209, option“Yes,” for each identified parameter in the obtained trigger. In someembodiments, upon performing the analysis along each identifiedparameter, the pay network server may generate an analytics resultspackage for the merchant, e.g., 2210. The pay network server may providethe analytics results to the merchant acquirer server according to theinstructions provided in the trigger, or using default settings ifavailable. In some embodiments, the merchant/acquirer server may be ableto display the analytics results via a display system, e.g., 2211,and/or store, e.g., 2212, the analytics results to a merchant/acquirerdatabase.

DPO Controller

FIG. 23 shows a block diagram illustrating embodiments of a DPOcontroller 2301. In this embodiment, the DPO controller 2301 may serveto aggregate, process, store, search, serve, identify, instruct,generate, match, and/or facilitate interactions with a computer throughvarious technologies, and/or other related data.

Typically, users, e.g., 2333 a, which may be people and/or othersystems, may engage information technology systems (e.g., computers) tofacilitate information processing. In turn, computers employ processorsto process information; such processors 2303 may be referred to ascentral processing units (CPU). One form of processor is referred to asa microprocessor. CPUs use communicative circuits to pass binary encodedsignals acting as instructions to enable various operations. Theseinstructions may be operational and/or data instructions containingand/or referencing other instructions and data in various processoraccessible and operable areas of memory 2329 (e.g., registers, cachememory, random access memory, etc.). Such communicative instructions maybe stored and/or transmitted in batches (e.g., batches of instructions)as programs and/or data components to facilitate desired operations.These stored instruction codes, e.g., programs, may engage the CPUcircuit components and other motherboard and/or system components toperform desired operations. One type of program is a computer operatingsystem, which, may be executed by CPU on a computer; the operatingsystem enables and facilitates users to access and operate computerinformation technology and resources. Some resources that may beemployed in information technology systems include: input and outputmechanisms through which data may pass into and out of a computer;memory storage into which data may be saved; and processors by whichinformation may be processed. These information technology systems maybe used to collect data for later retrieval, analysis, and manipulation,which may be facilitated through a database program. These informationtechnology systems provide interfaces that allow users to access andoperate various system components.

In one embodiment, the DPO controller 2301 may be connected to and/orcommunicate with entities such as, but not limited to: one or more usersfrom user input devices 2311; peripheral devices 2312; an optionalcryptographic processor device 2328; and/or a communications network2313. For example, the DPO controller 2301 may be connected to and/orcommunicate with users, e.g., 2333 a, operating client device(s), e.g.,2333 b, including, but not limited to, personal computer(s), server(s)and/or various mobile device(s) including, but not limited to, cellulartelephone(s), smartphone(s) (e.g., iPhone®, Blackberry®, AndroidOS-based phones etc.), tablet computer(s) (e.g., Apple iPad™, HP Slate™,Motorola Xoom™, etc.), eBook reader(s) (e.g., Amazon Kindle™, Barnes andNoble's Nook™ eReader, etc.), laptop computer(s), notebook(s),netbook(s), gaming console(s) (e.g., XBOX Live™, Nintendo® DS, SonyPlayStation® Portable, etc.), portable scanner(s), and/or the like.

Networks are commonly thought to comprise the interconnection andinteroperation of clients, servers, and intermediary nodes in a graphtopology. It should be noted that the term “server” as used throughoutthis application refers generally to a computer, other device, program,or combination thereof that processes and responds to the requests ofremote users across a communications network. Servers serve theirinformation to requesting “clients.” The term “client” as used hereinrefers generally to a computer, program, other device, user and/orcombination thereof that is capable of processing and making requestsand obtaining and processing any responses from servers across acommunications network. A computer, other device, program, orcombination thereof that facilitates, processes information andrequests, and/or furthers the passage of information from a source userto a destination user is commonly referred to as a “node.” Networks aregenerally thought to facilitate the transfer of information from sourcepoints to destinations. A node specifically tasked with furthering thepassage of information from a source to a destination is commonly calleda “router.” There are many forms of networks such as Local Area Networks(LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks(WLANs), etc. For example, the Internet is generally accepted as beingan interconnection of a multitude of networks whereby remote clients andservers may access and interoperate with one another.

The DPO controller 2301 may be based on computer systems that maycomprise, but are not limited to, components such as: a computersystemization 2302 connected to memory 2329.

Computer Systemization

A computer systemization 2302 may comprise a clock 2330, centralprocessing unit (“CPU(s)” and/or “processor(s)” (these terms are usedinterchangeable throughout the disclosure unless noted to the contrary))2303, a memory 2329 (e.g., a read only memory (ROM) 2306, a randomaccess memory (RAM) 2305, etc.), and/or an interface bus 2307, and mostfrequently, although not necessarily, are all interconnected and/orcommunicating through a system bus 2304 on one or more (mother)board(s)2302 having conductive and/or otherwise transportive circuit pathwaysthrough which instructions (e.g., binary encoded signals) may travel toeffectuate communications, operations, storage, etc. The computersystemization may be connected to a power source 2386; e.g., optionallythe power source may be internal. Optionally, a cryptographic processor2326 and/or transceivers (e.g., ICs) 2374 may be connected to the systembus. In another embodiment, the cryptographic processor and/ortransceivers may be connected as either internal and/or externalperipheral devices 2312 via the interface bus I/O. In turn, thetransceivers may be connected to antenna(s) 2375, thereby effectuatingwireless transmission and reception of various communication and/orsensor protocols; for example the antenna(s) may connect to: a TexasInstruments WiLink WL1283 transceiver chip (e.g., providing 802.11n,Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing DPOcontroller to determine its location)); Broadcom BCM4329FKUBGtransceiver chip (e.g., providing 802.11n, Bluetooth 2.1+EDR, FM, etc.);a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an InfineonTechnologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPAcommunications); and/or the like. The system clock typically has acrystal oscillator and generates a base signal through the computersystemization's circuit pathways. The clock is typically coupled to thesystem bus and various clock multipliers that will increase or decreasethe base operating frequency for other components interconnected in thecomputer systemization. The clock and various components in a computersystemization drive signals embodying information throughout the system.Such transmission and reception of instructions embodying informationthroughout a computer systemization may be commonly referred to ascommunications. These communicative instructions may further betransmitted, received, and the cause of return and/or replycommunications beyond the instant computer systemization to:communications networks, input devices, other computer systemizations,peripheral devices, and/or the like. It should be understood that inalternative embodiments, any of the above components may be connecteddirectly to one another, connected to the CPU, and/or organized innumerous variations employed as exemplified by various computer systems.

The CPU comprises at least one high-speed data processor adequate toexecute program components for executing user and/or system-generatedrequests. Often, the processors themselves will incorporate variousspecialized processing units, such as, but not limited to: integratedsystem (bus) controllers, memory management control units, floatingpoint units, and even specialized processing sub-units like graphicsprocessing units, digital signal processing units, and/or the like.Additionally, processors may include internal fast access addressablememory, and be capable of mapping and addressing memory 2329 beyond theprocessor itself; internal memory may include, but is not limited to:fast registers, various levels of cache memory (e.g., level 1, 2, 3,etc.), RAM, etc. The processor may access this memory through the use ofa memory address space that is accessible via instruction address, whichthe processor can construct and decode allowing it to access a circuitpath to a specific memory address space having a memory state. The CPUmay be a microprocessor such as: AMD's Athlon, Duron and/or Opteron;ARM's application, embedded and secure processors; IBM and/or Motorola'sDragonBall and PowerPC; IBM's and Sony's Cell processor; Intel'sCeleron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or thelike processor(s). The CPU interacts with memory through instructionpassing through conductive and/or transportive conduits (e.g., (printed)electronic and/or optic circuits) to execute stored instructions (i.e.,program code) according to conventional data processing techniques. Suchinstruction passing facilitates communication within the DPO controllerand beyond through various interfaces. Should processing requirementsdictate a greater amount speed and/or capacity, distributed processors(e.g., Distributed DPO), mainframe, multi-core, parallel, and/orsuper-computer architectures may similarly be employed. Alternatively,should deployment requirements dictate greater portability, smallerPersonal Digital Assistants (PDAs) may be employed.

Depending on the particular implementation, features of the DPO may beachieved by implementing a microcontroller such as CAST's R8051XC2microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or thelike. Also, to implement certain features of the DPO, some featureimplementations may rely on embedded components, such as:Application-Specific Integrated Circuit (“ASIC”), Digital SignalProcessing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or thelike embedded technology. For example, any of the DPO componentcollection (distributed or otherwise) and/or features may be implementedvia the microprocessor and/or via embedded components; e.g., via ASIC,coprocessor, DSP, FPGA, and/or the like. Alternately, someimplementations of the DPO may be implemented with embedded componentsthat are configured and used to achieve a variety of features or signalprocessing.

Depending on the particular implementation, the embedded components mayinclude software solutions, hardware solutions, and/or some combinationof both hardware/software solutions. For example, DPO features discussedherein may be achieved through implementing FPGAs, which are asemiconductor devices containing programmable logic components called“logic blocks”, and programmable interconnects, such as the highperformance FPGA Virtex series and/or the low cost Spartan seriesmanufactured by Xilinx. Logic blocks and interconnects can be programmedby the customer or designer, after the FPGA is manufactured, toimplement any of the DPO features. A hierarchy of programmableinterconnects allow logic blocks to be interconnected as needed by theDPO system designer/administrator, somewhat like a one-chip programmablebreadboard. An FPGA's logic blocks can be programmed to perform theoperation of basic logic gates such as AND, and XOR, or more complexcombinational operators such as decoders or simple mathematicaloperations. In most FPGAs, the logic blocks also include memoryelements, which may be circuit flip-flops or more complete blocks ofmemory. In some circumstances, the DPO may be developed on regular FPGAsand then migrated into a fixed version that more resembles ASICimplementations. Alternate or coordinating implementations may migrateDPO controller features to a final ASIC instead of or in addition toFPGAs. Depending on the implementation all of the aforementionedembedded components and microprocessors may be considered the “CPU”and/or “processor” for the DPO.

Power Source

The power source 2386 may be of any standard form for powering smallelectronic circuit board devices such as the following power cells:alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium,solar cells, and/or the like. Other types of AC or DC power sources maybe used as well. In the case of solar cells, in one embodiment, the caseprovides an aperture through which the solar cell may capture photonicenergy. The power cell 2386 is connected to at least one of theinterconnected subsequent components of the DPO thereby providing anelectric current to all subsequent components. In one example, the powersource 2386 is connected to the system bus component 2304. In analternative embodiment, an outside power source 2386 is provided througha connection across the I/O 2308 interface. For example, a USB and/orIEEE 1394 connection carries both data and power across the connectionand is therefore a suitable source of power.

Interface Adapters

Interface bus(ses) 2307 may accept, connect, and/or communicate to anumber of interface adapters, conventionally although not necessarily inthe form of adapter cards, such as but not limited to: input outputinterfaces (I/O) 2308, storage interfaces 2309, network interfaces 2310,and/or the like. Optionally, cryptographic processor interfaces 2327similarly may be connected to the interface bus. The interface busprovides for the communications of interface adapters with one anotheras well as with other components of the computer systemization.Interface adapters are adapted for a compatible interface bus. Interfaceadapters conventionally connect to the interface bus via a slotarchitecture. Conventional slot architectures may be employed, such as,but not limited to: Accelerated Graphics Port (AGP), Card Bus,(Extended) Industry Standard Architecture ((E)ISA), Micro ChannelArchitecture (MCA), NuBus, Peripheral Component Interconnect (Extended)(PCI(X)), PCI Express, Personal Computer Memory Card InternationalAssociation (PCMCIA), and/or the like.

Storage interfaces 2309 may accept, communicate, and/or connect to anumber of storage devices such as, but not limited to: storage devices2314, removable disc devices, and/or the like. Storage interfaces mayemploy connection protocols such as, but not limited to: (Ultra)(Serial) Advanced Technology Attachment (Packet Interface) ((Ultra)(Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE),Institute of Electrical and Electronics Engineers (IEEE) 1394, fiberchannel, Small Computer Systems Interface (SCSI), Universal Serial Bus(USB), and/or the like.

Network interfaces 2310 may accept, communicate, and/or connect to acommunications network 2313. Through a communications network 2313, theDPO controller is accessible through remote clients 2333 b (e.g.,computers with web browsers) by users 2333 a. Network interfaces mayemploy connection protocols such as, to but not limited to: directconnect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/orthe like), Token Ring, wireless connection such as IEEE 802.11a-x,and/or the like. Should processing requirements dictate a greater amountspeed and/or capacity, distributed network controllers (e.g.,Distributed DPO), architectures may similarly be employed to pool, loadbalance, and/or otherwise increase the communicative bandwidth requiredby the DPO controller. A communications network may be any one and/orthe combination of the following: a direct interconnection; theInternet; a Local Area Network (LAN); a Metropolitan Area Network (MAN);an Operating Missions as Nodes on the Internet (OMNI); a secured customconnection; a Wide Area Network (WAN); a wireless network (e.g.,employing protocols such as, but not limited to a Wireless ApplicationProtocol (WAP), I-mode, and/or the like); and/or the like. A networkinterface may be regarded as a specialized form of an input outputinterface. Further, multiple network interfaces 2310 may be used toengage with various communications network types 2313. For example,multiple network interfaces may be employed to allow for thecommunication over broadcast, multicast, and/or unicast networks.

Input Output interfaces (I/O) 2308 may accept, communicate, and/orconnect to user input devices 2311, peripheral devices 2312,cryptographic processor devices 2328, and/or the like. I/O may employconnection protocols such as, but not limited to: audio: analog,digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus(ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared;joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; videointerface: Apple Desktop Connector (ADC), BNC, coaxial, component,composite, digital, Digital Visual Interface (DVI), high-definitionmultimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or thelike; wireless transceivers: 802.m/b/g/n/x; Bluetooth; cellular (e.g.,code division multiple access (CDMA), high speed packet access(HSPA(+)), high-speed downlink packet access (HSDPA), global system formobile communications (GSM), long term evolution (LTE), WiMax, etc.);and/or the like. One typical output device may include a video display,which typically comprises a Cathode Ray Tube (CRT) or Liquid CrystalDisplay (LCD) based monitor with an interface (e.g., DVI circuitry andcable) that accepts signals from a video interface, may be used. Thevideo interface composites information generated by a computersystemization and generates video signals based on the compositedinformation in a video memory frame. Another output device is atelevision set, which accepts signals from a video interface. Typically,the video interface provides the composited video information through avideo connection interface that accepts a video display interface (e.g.,an RCA composite video connector accepting an RCA composite video cable;a DVI connector accepting a DVI display cable, etc.).

User input devices 2311 often are a type of peripheral device 2312 (seebelow) and may include: card readers, dongles, finger print readers,gloves, graphics tablets, joysticks, keyboards, microphones, mouse(mice), remote controls, retina readers, touch screens (e.g.,capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g.,accelerometers, ambient light, GPS, gyroscopes, proximity, etc.),styluses, and/or the like.

Peripheral devices 2312 may be connected and/or communicate to I/Oand/or other facilities of the like such as network interfaces, storageinterfaces, directly to the interface bus, system bus, the CPU, and/orthe like. Peripheral devices may be external, internal and/or part ofthe DPO controller. Peripheral devices may include: antenna, audiodevices (e.g., line-in, line-out, microphone input, speakers, etc.),cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copyprotection, ensuring secure transactions with a digital signature,and/or the like), external processors (for added capabilities; e.g.,crypto devices 2328), force-feedback devices (e.g., vibrating motors),network interfaces, printers, scanners, storage devices, transceivers(e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors,etc.), video sources, visors, and/or the like. Peripheral devices ofteninclude types of input devices (e.g., cameras).

It should be noted that although user input devices and peripheraldevices may be employed, the DPO controller may be embodied as anembedded, dedicated, and/or monitor-less (i.e., headless) device,wherein access would be provided over a network interface connection.

Cryptographic units such as, but not limited to, microcontrollers,processors 2326, interfaces 2327, and/or devices 2328 may be attached,and/or communicate with the DPO controller. A MC68HC16 microcontroller,manufactured by Motorola Inc., may be used for and/or withincryptographic units. The MC68HC16 microcontroller utilizes a 16-bitmultiply-and-accumulate instruction in the 16 MHz configuration andrequires less than one second to perform a 512-bit RSA private keyoperation. Cryptographic units support the authentication ofcommunications from interacting agents, as well as allowing foranonymous transactions. Cryptographic units may also be configured aspart of the CPU. Equivalent microcontrollers and/or processors may alsobe used. Other commercially available specialized cryptographicprocessors include: the Broadcom's CryptoNetX and other SecurityProcessors; nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series;Semaphore Communications' 40 MHz Roadrunner 184; Sun's CryptographicAccelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line,which is capable of performing 500+ MB/s of cryptographic instructions;VLSI Technology's 33 MHz 6868; and/or the like.

Memory

Generally, any mechanization and/or embodiment allowing a processor toaffect the storage and/or retrieval of information is regarded as memory2329. However, memory is a fungible technology and resource, thus, anynumber of memory embodiments may be employed in lieu of or in concertwith one another. It is to be understood that the DPO controller and/ora computer systemization may employ various forms of memory 2329. Forexample, a computer systemization may be configured wherein theoperation of on-chip CPU memory (e.g., registers), RAM, ROM, and anyother storage devices are provided by a paper punch tape or paper punchcard mechanism; however, such an embodiment would result in an extremelyslow rate of operation. In a typical configuration, memory 2329 willinclude ROM 2306, RAM 2305, and a storage device 2314. A storage device2314 may be any conventional computer system storage. Storage devicesmay include a drum; a (fixed and/or removable) magnetic disk drive; amagneto-optical drive; an optical drive (i.e., Blueray, CDROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); anarray of devices (e.g., Redundant Array of Independent Disks (RAID));solid state memory devices (USB memory, solid state drives (SSD), etc.);other processor-readable storage mediums; and/or other devices of thelike. Thus, a computer systemization generally requires and makes use ofmemory.

Component Collection

The memory 2329 may contain a collection of program and/or databasecomponents and/or data such as, but not limited to: operating systemcomponent(s) 2315 (operating system); information server component(s)2316 (information server); user interface component(s) 2317 (userinterface); Web browser component(s) 2318 (Web browser); database(s)2319; mail server component(s) 2321; mail client component(s) 2322;cryptographic server component(s) 2320 (cryptographic server); the DPOcomponent(s) 2335; and/or the like (i.e., collectively a componentcollection). These components may be stored and accessed from thestorage devices and/or from storage devices accessible through aninterface bus. Although non-conventional program components such asthose in the component collection, typically, are stored in a localstorage device 2314, they may also be loaded and/or stored in memorysuch as: peripheral devices, RAM, remote storage facilities through acommunications network, ROM, various forms of memory, and/or the like.

Operating System

The operating system component 2315 is an executable program componentfacilitating the operation of the DPO controller. Typically, theoperating system facilitates access of I/O, network interfaces,peripheral devices, storage devices, and/or the like. The operatingsystem may be a highly fault tolerant, scalable, and secure system suchas: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix andUnix-like system distributions (such as AT&T's UNIX; Berkley SoftwareDistribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/orthe like; Linux distributions such as Red Hat, Ubuntu, and/or the like);and/or the like operating systems. However, more limited and/or lesssecure operating systems also may be employed such as Apple MacintoshOS, IBM OS/2, Microsoft DOS, Microsoft Windows2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/orthe like. An operating system may communicate to and/or with othercomponents in a component collection, including itself, and/or the like.Most frequently, the operating system communicates with other programcomponents, user interfaces, and/or the like. For example, the operatingsystem may contain, communicate, generate, obtain, and/or provideprogram component, system, user, and/or data communications, requests,and/or responses. The operating system, once executed by the CPU, mayenable the interaction with communications networks, data, I/O,peripheral devices, program components, memory, user input devices,and/or the like. The operating system may provide communicationsprotocols that allow the DPO controller to communicate with otherentities through a communications network 2313. Various communicationprotocols may be used by the DPO controller as a subcarrier transportmechanism for interaction, such as, but not limited to: multicast,TCP/IP, UDP, unicast, and/or the like.

Information Server

An information server component 2316 is a stored program component thatis executed by a CPU. The information server may be a conventionalInternet information server such as, but not limited to Apache SoftwareFoundation's Apache, Microsoft's Internet Information Server, and/or thelike. The information server may allow for the execution of programcomponents through facilities such as Active Server Page (ASP), ActiveX,(ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface(CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH,Java, JavaScript, Practical Extraction Report Language (PERL), HypertextPre-Processor (PHP), pipes, Python, wireless application protocol (WAP),WebObjects, and/or the like. The information server may support securecommunications protocols such as, but not limited to, File TransferProtocol (PTP); HyperText Transfer Protocol (HTTP); Secure HypertextTransfer Protocol (HTTPS), Secure Socket Layer (SSL), messagingprotocols (e.g., America Online (AOL) Instant Messenger (AIM),Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), MicrosoftNetwork (MSN) Messenger Service, Presence and Instant Messaging Protocol(PRIM), Internet Engineering Task Force's (IETF's) Session InitiationProtocol (SIP), SIP for Instant Messaging and Presence LeveragingExtensions (SIMPLE), open XML-based Extensible Messaging and PresenceProtocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) InstantMessaging and Presence Service (IMPS)), Yahoo! Instant MessengerService, and/or the like. The information server provides results in theform of Web pages to Web browsers, and allows for the manipulatedgeneration of the Web pages through interaction with other programcomponents. After a Domain Name System (DNS) resolution portion of anHTTP request is resolved to a particular information server, theinformation server resolves requests for information at specifiedlocations on the DPO controller based on the remainder of the HTTPrequest. For example, a request such ashttp://123.124.125.126/myInformation.html might have the IP portion ofthe request “123.124.125.126” resolved by a DNS server to an informationserver at that IP address; that information server might in turn furtherparse the http request for the “/myInformation.html” portion of therequest and resolve it to a location in memory containing theinformation “myInformation.html.” Additionally, other informationserving protocols may be employed across various ports, e.g., FTPcommunications across port 21, and/or the like. An information servermay communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the information server communicates with the DPO database2319, operating systems, other program components, user interfaces, Webbrowsers, and/or the like.

Access to the DPO database may be achieved through a number of databasebridge mechanisms such as through scripting languages as enumeratedbelow (e.g., CGI) and through inter-application communication channelsas enumerated below (e.g., CORBA, WebObjects, etc.). Any data requeststhrough a Web browser are parsed through the bridge mechanism intoappropriate grammars as required by the DPO. In one embodiment, theinformation server would provide a Web form accessible by a Web browser.Entries made into supplied fields in the Web form are tagged as havingbeen entered into the particular fields, and parsed as such. The enteredterms are then passed along with the field tags, which act to instructthe parser to generate queries directed to appropriate tables and/orfields. In one embodiment, the parser may generate queries in standardSQL by instantiating a search string with the proper join/selectcommands based on the tagged text entries, wherein the resulting commandis provided over the bridge mechanism to the DPO as a query. Upongenerating query results from the query, the results are passed over thebridge mechanism, and may be parsed formatting and generation of a newresults Web page by the bridge mechanism. Such a new results Web page isthen provided to the information server, which may supply it to therequesting Web browser.

Also, an information server may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses.

User Interface

Computer interfaces in some respects are similar to automobile operationinterfaces. Automobile operation interface elements such as steeringwheels, gearshifts, and speedometers facilitate the access, operation,and display of automobile resources, and status. Computer interactioninterface elements such as check boxes, cursors, menus, scrollers, andwindows (collectively and commonly referred to as widgets) similarlyfacilitate the access, capabilities, operation, and display of data andcomputer hardware and operating system resources, and status. Operationinterfaces are commonly called user interfaces. Graphical userinterfaces (GUIs) such as the Apple Macintosh Operating System's Aqua,IBM's OS/2, Microsoft's Windows2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix'sX-Windows (e.g., which may include additional Unix graphic interfacelibraries and layers such as K Desktop Environment (KDE), mythTV and GNUNetwork Object Model Environment (GNOME)), web interface libraries(e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interfacelibraries such as, but not limited to, Dojo, jQuery(UI), MooTools,Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any ofwhich may be used and) provide a baseline and means of accessing anddisplaying information graphically to users.

A user interface component 2317 is a stored program component that isexecuted by a CPU. The user interface may be a conventional graphic userinterface as provided by, with, and/or atop operating systems and/oroperating environments such as already discussed. The user interface mayallow for the display, execution, interaction, manipulation, and/oroperation of program components and/or system facilities through textualand/or graphical facilities. The user interface provides a facilitythrough which users may affect, interact, and/or operate a computersystem. A user interface may communicate to and/or with other componentsin a component collection, including itself, and/or facilities of thelike. Most frequently, the user interface communicates with operatingsystems, other program components, and/or the like. The user interfacemay contain, communicate, generate, obtain, and/or provide programcomponent, system, user, and/or data communications, requests, and/orresponses.

Web Browser

A Web browser component 2318 is a stored program component that isexecuted by a CPU. The Web browser may be a conventional hypertextviewing application such as Microsoft Internet Explorer or NetscapeNavigator. Secure Web browsing may be supplied with 128 bit (or greater)encryption by way of HTTPS, SSL, and/or the like. Web browsers allowingfor the execution of program components through facilities such asActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-inAPIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or thelike. Web browsers and like information access tools may be integratedinto PDAs, cellular telephones, and/or other mobile devices. A Webbrowser may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the Web browser communicates with information servers,operating systems, integrated program components (e.g., plug-ins),and/or the like; e.g., it may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses. Also, in place of a Webbrowser and information server, a combined application may be developedto perform similar operations of both. The combined application wouldsimilarly affect the obtaining and the provision of information tousers, user agents, and/or the like from the DPO enabled nodes. Thecombined application may be nugatory on systems employing standard Webbrowsers.

Mail Server

A mail server component 2321 is a stored program component that isexecuted by a CPU 2303. The mail server may be a conventional Internetmail server such as, but not limited to sendmail, Microsoft Exchange,and/or the like. The mail server may allow for the execution of programcomponents through facilities such as ASP, ActiveX, (ANSI) (Objective-)C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes,Python, WebObjects, and/or the like. The mail server may supportcommunications protocols such as, but not limited to: Internet messageaccess protocol (IMAP), Messaging Application Programming Interface(MAPI)/Microsoft Exchange, post office protocol (POP3), simple mailtransfer protocol (SMTP), and/or the like. The mail server can route,forward, and process incoming and outgoing mail messages that have beensent, relayed and/or otherwise traversing through and/or to the DPO.

Access to the DPO mail may be achieved through a number of APIs offeredby the individual Web server components and/or the operating system.

Also, a mail server may contain, communicate, generate, obtain, and/orprovide program component, system, user, and/or data communications,requests, information, and/or responses.

Mail Client

A mail client component 2322 is a stored program component that isexecuted by a CPU 2303. The mail client may be a conventional mailviewing application such as Apple Mail, Microsoft Entourage, MicrosoftOutlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or thelike. Mail clients may support a number of transfer protocols, such as:IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, themail client communicates with mail servers, operating systems, othermail clients, and/or the like; e.g., it may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, information, and/or responses. Generally,the mail client provides a facility to compose and transmit electronicmail messages.

Cryptographic Server

A cryptographic server component 2320 is a stored program component thatis executed by a CPU 2303, cryptographic processor 2326, cryptographicprocessor interface 2327, cryptographic processor device 2328, and/orthe like. Cryptographic processor interfaces will allow for expeditionof encryption and/or decryption requests by the cryptographic component;however, the cryptographic component, alternatively, may run on aconventional CPU. The cryptographic component allows for the encryptionand/or decryption of provided data. The cryptographic component allowsfor both symmetric and asymmetric (e.g., Pretty Good Protection (PGP))encryption and/or decryption. The cryptographic component may employcryptographic techniques such as, but not limited to: digitalcertificates (e.g., X.509 authentication framework), digital signatures,dual signatures, enveloping, password access protection, public keymanagement, and/or the like. The cryptographic component will facilitatenumerous (encryption and/or decryption) security protocols such as, butnot limited to: checksum, Data Encryption Standard (DES), EllipticalCurve Encryption (ECC), International Data Encryption Algorithm (IDEA),Message Digest 5 (MD5, which is a one way hash operation), passwords,Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption andauthentication system that uses an algorithm developed in 1977 by RonRivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA),Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS),and/or the like. Employing such encryption security protocols, the DPOmay encrypt all incoming and/or outgoing communications and may serve asnode within a virtual private network (VPN) with a wider communicationsnetwork. The cryptographic component facilitates the process of“security authorization” whereby access to a resource is inhibited by asecurity protocol wherein the cryptographic component effects authorizedaccess to the secured resource. In addition, the cryptographic componentmay provide unique identifiers of content, e.g., employing and MD5 hashto obtain a unique signature for an digital audio file. A cryptographiccomponent may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Thecryptographic component supports encryption schemes allowing for thesecure transmission of information across a communications network toenable the DPO component to engage in secure transactions if so desired.The cryptographic component facilitates the secure accessing ofresources on the DPO and facilitates the access of secured resources onremote systems; i.e., it may act as a client and/or server of securedresources. Most frequently, the cryptographic component communicateswith information servers, operating systems, other program components,and/or the like. The cryptographic component may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, and/or responses.

The DPO Database

The DPO database component 2319 may be embodied in a database and itsstored data. The database is a stored program component, which isexecuted by the CPU; the stored program component portion configuringthe CPU to process the stored data. The database may be a conventional,fault tolerant, relational, scalable, secure database such as Oracle orSybase. Relational databases are an extension of a flat file. Relationaldatabases consist of a series of related tables. The tables areinterconnected via a key field. Use of the key field allows thecombination of the tables by indexing against the key field; i.e., thekey fields act as dimensional pivot points for combining informationfrom various tables. Relationships generally identify links maintainedbetween tables by matching primary keys. Primary keys represent fieldsthat uniquely identify the rows of a table in a relational database.More precisely, they uniquely identify rows of a table on the “one” sideof a one-to-many relationship.

Alternatively, the DPO database may be implemented using variousstandard data-structures, such as an array, hash, (linked) list, struct,structured text file (e.g., XML), table, and/or the like. Suchdata-structures may be stored in memory and/or in (structured) files. Inanother alternative, an object-oriented database may be used, such asFrontier, ObjectStore, Poet, Zope, and/or the like. Object databases caninclude a number of object collections that are grouped and/or linkedtogether by common attributes; they may be related to other objectcollections by some common attributes. Object-oriented databases performsimilarly to relational databases with the exception that objects arenot just pieces of data but may have other types of capabilitiesencapsulated within a given object. If the DPO database is implementedas a data-structure, the use of the DPO database 2319 may be integratedinto another component such as the DPO component 2335. Also, thedatabase may be implemented as a mix of data structures, objects, andrelational structures. Databases may be consolidated and/or distributedin countless variations through standard data processing techniques.Portions of databases, e.g., tables, may be exported and/or imported andthus decentralized and/or integrated.

In one embodiment, the database component 2319 includes several tables2319 a-o. A Users table 2319 a may include fields such as, but notlimited to: user_id, ssn, dob, first_name, last_name, age, state,address_firstline, address_secondline, zipcode, devices_list,contact_info, contact_type, alt_contact_info, alt_contact_type, and/orthe like. The Users table may support and/or track multiple entityaccounts on a DPO. A Devices table 2319 b may include fields such as,but not limited to: device_ID, device_name, device_IP, device_MAC,device_type, device_model, device_version, device_OS, device_apps_list,device_securekey, wallet_app_installed_flag, and/or the like. An Appstable 2319 c may include fields such as, but not limited to: app_ID,app_name, app_type, app_dependencies, and/or the like. An Accounts table2319 d may include fields such as, but not limited to: account_number,account_security_code, account_name, issuer_acquirer_flag, issuer_name,acquirer_name, account_address, routing_number, access_API_call,linked_wallets_list, and/or the like. A Merchants table 2319 e mayinclude fields such as, but not limited to: merchant_id, merchant_name,merchant_address, ip_address, mac_address, auth_key, port_num,security_settings_list, and/or the like. An issuers table 2319 f mayinclude fields such as, but not limited to: issuer_id, issuer_name,issuer_address, ip_address, mac_address, auth_key, port_num,security_settings_list, and/or the like. An Acquirers table 2319 g mayinclude fields such as, but not limited to: account_firstname,account_lastname, account_type, account_num, account_balance_list,billingaddress_line1, billingaddress_line2, billing_zipcode,billing_state, shipping_preferences, shippingaddress_line1,shippingaddress_line2, shipping_zipcode, shipping_state, and/or thelike. A Pay Gateways table 2319 h may include fields such as, but notlimited to: service_type, service_list, secure_ley, access_API_list,API_template_array, paygate_id, paygate_address, paygate_URL,paygate_name, payNET_id, payNET_address, payNET_URL, payNET_name, and/orthe like. A Transactions table 2319 i may include fields such as, butnot limited to: order_id, user_id, timestamp, transaction_cost,purchase_details_list, num_products, products_list, product_type,product_params_list, product_title, product_summary, quantity, user_id,client_id, client_ip, client_type, client_model, operating_system,os_version, app_installed_flag, user_id, account_firstname,account_lastname, account_type, account_num,account_priority_account_ratio, billingaddress_line1,billingaddress_line2, billing_zipcode, billing_state,shipping_preferences, shippingaddress_line1, shippingaddress_line2,shipping_zipcode, shipping_state, merchant_id, merchant_name,merchant_auth_key, and/or the like. A Batches table 2319 j may includefields such as, but not limited to: batch_id, transaction_id_list,timestamp_list, cleared_flag_list, clearance_trigger_settings, and/orthe like. A Ledgers table 2319 k may include fields such as, but notlimited to: request_id, timestamp, deposit_amount, batch_id,transaction_id, clear_flag, deposit_account, transaction_summary,payor_name, payor_account, and/or the like. A Products table 2319 l mayinclude fields such as, but not limited to: product_ID, product_title,product_attributes_list, product_price, tax_info_list,related_products_list, offers_list, discounts_list, rewards_list,merchants_list, merchant_availability_list, and/or the like. An Offerstable 2319 m may include fields such as, but not limited to: offer_ID,offer_title, offer_attributes_list, offer_price, offer_expiry,related_products_list, discounts_list, rewards_list, merchants_list,merchant_availability_list, and/or the like. A Behavior Data table 2319n may include fields such as, but not limited to: user_id, user_name,user_gaming_times_hist, user_gaming_list,user_product_purchase_categories_list, and/or the like. An Analyticstable 2319 o may include fields such as, but not limited to:merchant_id, timestamp, report_type, report_criterion_list,algorithm_list, results_array, and/or the like. A Social Graph table2319 p may include fields such as, but not limited to: user_id,user_name, user_graph_list, graph_weight_list, user_friend_list,user_enemy_list, user_posts_list, and/or the like. A Recommendationstable 2319 q may include fields such as, but not limited to:recommendation_id, recommendation_name, recommendsation_type, user_id,products_list, pricing_list, expriry_date, tax_info, and/or the like. ACurrency Exchange table 2319 r may include fields such as, but notlimited to: currency_id, currency_name, currency_type,algorithm_pref_list, threshold_values, base_currency, and/or the like. AGeographical Customizations table 2319 s may include fields such as, butnot limited to: geo_id, geo_name, geo_UI_customizations_list,geo_currnecy_customizations_list, and/or the like.

In one embodiment, the DPO database may interact with other databasesystems. For example, employing a distributed database system, queriesand data access by search DPO component may treat the combination of theDPO database, an integrated data security layer database as a singledatabase entity.

In one embodiment, user programs may contain various user interfaceprimitives, which may serve to update the DPO. Also, various accountsmay require custom database tables depending upon the environments andthe types of clients the DPO may need to serve. It should be noted thatany unique fields may be designated as a key field throughout. In analternative embodiment, these tables have been decentralized into theirown databases and their respective database controllers (i.e.,individual database controllers for each of the above tables). Employingstandard data processing techniques, one may further distribute thedatabases over several computer systemizations and/or storage devices.Similarly, configurations of the decentralized database controllers maybe varied by consolidating and/or distributing the various databasecomponents 2319 a-o. The DPO may be configured to keep track of varioussettings, inputs, and parameters via database controllers.

The DPO database may communicate to and/or with other components in acomponent collection, including itself, and/or facilities of the like.Most frequently, the DPO database communicates with the DPO component,other program components, and/or the like. The database may contain,retain, and provide information regarding other nodes and data.

The DPOs

The DPO component 2335 is a stored program component that is executed bya CPU. In one embodiment, the DPO component incorporates any and/or allcombinations of the aspects of the DPO discussed in the previousfigures. As such, the DPO affects accessing, obtaining and the provisionof information, services, transactions, and/or the like across variouscommunications networks.

The DPO component may transform requests for on-demand and flexiblemonetization and related services via DPO components into currencytransfers, purchase receipt notifications, social networkingcommunications and transaction analytics reports, and/or the like anduse of the DPO. In one embodiment, the DPO component 2335 takes inputs(e.g., catalog browsing input 711, product cart data 729, productcatalog 720, social search results 717, product selection input 725,checkout request input 911, product data 915, service authorizationresponse 1115, service data 1121, wallet access input 1511, transactionauthorization input 1514, payment gateway address 1518, payment networkaddress 1522, issuer server address(es) 1525, user account(s) data 1528,user profile data 1713, batch data 1912, payment network address 1916,issuer server address(es) 1924, payment ledger, merchant account data1931, merchant transactions data 2114, and/or the like) etc., andtransforms the inputs via various components (e.g., UPC 2341, PTA 2342,PTC 343, PCB 2344, FMS 2345, VCC 2346, DPO 2347, P2P-SNM 2348, GTVA2349, and/or the like), into outputs (e.g., product search response 723,display 724, updated product cart data 731, checkout data 917, display918, service authorization confirmation/retry message 1117, flexiblemonetization service request 1113, checkout widget 1124, cardauthorization request 1516, 1519, 1523, batch append data 1534, purchasereceipt 1535, social post confirmation 1717, user account credit command1723, social marketing credit notification 1724, display creditnotification 1725, batch payment request 1914, 1918, transaction data1920, payment command 1927, individual payment confirmation 1928, 1929,updated payment ledger, merchant account data 1933, analytics results2116, 2117, and/or the like).

The DPO component enabling access of information between nodes may bedeveloped by employing standard development tools and languages such as,but not limited to: Apache components, Assembly, ActiveX, binaryexecutables, (ANSI) (Objective-) C (++), C# and/or .NET, databaseadapters, CGI scripts, Java, JavaScript, mapping tools, procedural andobject oriented development tools, PERL, PHP, Python, shell scripts, SQLcommands, web application server extensions, web developmentenvironments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX &FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools;Prototype; script.aculo.us; Simple Object Access Protocol (SOAP);SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/orthe like. In one embodiment, the DPO server employs a cryptographicserver to encrypt and decrypt communications. The DPO component maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, theDPO component communicates with the DPO database, operating systems,other program components, and/or the like. The DPO may contain,communicate, generate, obtain, and/or provide program component, system,user, and/or data communications, requests, and/or responses.

Distributed DPOs

The structure and/or operation of any of the DPO node controllercomponents may be combined, consolidated, and/or distributed in anynumber of ways to facilitate development and/or deployment. Similarly,the component collection may be combined in any number of ways tofacilitate deployment and/or development. To accomplish this, one mayintegrate the components into a common code base or in a facility thatcan dynamically load the components on demand in an integrated fashion.

The component collection may be consolidated and/or distributed incountless variations through standard data processing and/or developmenttechniques. Multiple instances of any one of the program components inthe program component collection may be instantiated on a single node,and/or across numerous nodes to improve performance throughload-balancing and/or data-processing techniques. Furthermore, singleinstances may also be distributed across multiple controllers and/orstorage devices; e.g., databases. All program component instances andcontrollers working in concert may do so through standard dataprocessing communication techniques.

The configuration of the DPO controller will depend on the context ofsystem deployment. Factors such as, but not limited to, the budget,capacity, location, and/or use of the underlying hardware resources mayaffect deployment requirements and configuration. Regardless of if theconfiguration results in more consolidated and/or integrated programcomponents, results in a more distributed series of program components,and/or results in some combination between a consolidated anddistributed configuration, data may be communicated, obtained, and/orprovided. Instances of components consolidated into a common code basefrom the program component collection may communicate, obtain, and/orprovide data. This may be accomplished through intra-application dataprocessing communication techniques such as, but not limited to: datareferencing (e.g., pointers), internal messaging, object instancevariable communication, shared memory space, variable passing, and/orthe like.

If component collection components are discrete, separate, and/orexternal to one another, then communicating, obtaining, and/or providingdata with and/or to other components may be accomplished throughinter-application data processing communication techniques such as, butnot limited to: Application Program Interfaces (API) informationpassage; (distributed) Component Object Model ((D)COM), (Distributed)Object Linking and Embedding ((D)OLE), and/or the like), Common ObjectRequest Broker Architecture (CORBA), Jini local and remote applicationprogram interfaces, JavaScript Object Notation (JSON), Remote MethodInvocation (RMI), SOAP, process pipes, shared files, and/or the like.Messages sent between discrete component components forinter-application communication or within memory spaces of a singularcomponent for intra-application communication may be facilitated throughthe creation and parsing of a grammar. A grammar may be developed byusing development tools such as lex, yacc, XML, and/or the like, whichallow for grammar generation and parsing capabilities, which in turn mayform the basis of communication messages within and between components.

For example, a grammar may be arranged to recognize the tokens of anHTTP post command, e.g.:

-   -   w3c -post http:// . . . Value1

where Value1 is discerned as being a parameter because “http://” is partof the grammar syntax, and what follows is considered part of the postvalue. Similarly, with such a grammar, a variable “Value1” may beinserted into an “http://” post command and then sent. The grammarsyntax itself may be presented as structured data that is interpretedand/or otherwise used to generate the parsing mechanism (e.g., a syntaxdescription text file as processed by lex, yacc, etc.). Also, once theparsing mechanism is generated and/or instantiated, it itself mayprocess and/or parse structured data such as, but not limited to:character (e.g., tab) delineated text, HTML, structured text streams,XML, and/or the like structured data. In another embodiment,inter-application data processing protocols themselves may haveintegrated and/or readily available parsers (e.g., JSON, SOAP, and/orlike parsers) that may be employed to parse (e.g., communications) data.Further, the parsing grammar may be used beyond message parsing, but mayalso be used to parse: databases, data collections, data stores,structured data, and/or the like. Again, the desired configuration willdepend upon the context, environment, and requirements of systemdeployment.

For example, in some implementations, the DPO controller may beexecuting a PHP script implementing a Secure Sockets Layer (“SSL”)socket server via the information server, which listens to incomingcommunications on a server port to which a client may send data, e.g.,data encoded in JSON format. Upon identifying an incoming communication,the PHP script may read the incoming message from the client device,parse the received JSON-encoded text data to extract information fromthe JSON-encoded text data into PHP script variables, and store the data(e.g., client identifying information, etc.) and/or extractedinformation in a relational database accessible using the StructuredQuery Language (“SQL”). An exemplary listing, written substantially inthe form of PHP/SQL commands, to accept JSON-encoded input data from aclient device via a SSL connection, parse the data to extract variables,and store the data to a database, is provided below:

<?PHP header(‘Content-Type: text/plain’); $address = ‘192.168.0.100’;$port = 255; $sock = socket_create(AF_INET, SOCK_STREAM, 0);socket_bind($sock, $address, $port) or die(‘Could not bind to address’);socket_listen($sock); $client = socket_accept($sock); do {  $input = “”; $input = socket_read($client, 1024);  $data .= $input; } while($input!= “”); $obj = json_decode($data, true);mysql_connect(“201.408.185.132”,$DBserver,$password); // access databaseserver mysql_select(“CLIENT_DB.SQL”); // select database to appendmysql_query(“INSERT INTO UserTable (transmission) VALUES ($data)”); //add data to UserTable table in a CLIENT databasemysql_close(“CLIENT_DB.SQL”); // close connection to database ?>

Also, the following resources may be used to provide example embodimentsregarding SOAP parser implementation:

http://www.xav.com/perl/site/lib/SOAP/Parser.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/ index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide295.htm

and other parser implementations:

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/ index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide259.htm

all of which are hereby expressly incorporated by reference herein. Asnoted in FIGS. 1-2, “The Emergence of Monetization as a Service (MaaS)Platform,” the “Technical Overview of Platform” slides, and “PlaySpanMonetization Platform API”, from provisional application Ser. No.61/456,118, the figures and disclosure therein depict the following:

Additional non-limiting exemplary embodiments of the DPO highlightingnumerous further advantageous aspects include:

1. A virtual currency configuration processor-implemented methodembodiment, comprising:

-   -   obtaining a request to convert a sale price provided in a real        currency into a sale price in a virtual currency;    -   accessing a database to obtain at least one virtual currency        management rule provided by a merchant;    -   identifying one among the at least one obtained virtual currency        management rule to apply for converting the sale price provided        in the real currency into the sale price in the virtual        currency;    -   calculating, via a processor, the sale price in the virtual        currency from the sale price provided in the real currency using        the identified virtual currency management rule; and    -   providing the calculated sale price in the virtual currency in        response to the request.

2. The method of embodiment 1, wherein the identified virtual currencymanagement rule includes a discrete pricing rule that specifies a highervirtual-to-real currency exchange rate for larger amounts of the realcurrency.

3. The method of embodiment 2, wherein the discrete pricing ruleincludes pre-specified minimum and maximum virtual currency sale pricepoints, and discrete price points between the minimum and maximumvirtual currency sale price points.

4. The method of embodiment 3, wherein the price points are configurableby the merchant.

5. The method of embodiment 3, wherein the discrete price points areoptimized to maximize user purchasing behavior using analytics on prioruser purchase transactions.

6. The method of embodiment 1, wherein the identified virtual currencymanagement rule includes a smart pricing rule that specifies that thecalculated sale price in the virtual currency be rounded to at least onesignificant digit.

7. The method of embodiment 6, wherein the smart pricing rule specifiesthat the virtual-to-real currency exchange rate be rounded to at leastone significant digit.

8. The method of embodiment 6, wherein the smart pricing rule isconfigured to provide a rounded virtual currency sale price thatmaximizes user purchasing behavior.

9. The method of embodiment 8, wherein the smart pricing rule isconfigured using analytics on prior user purchase transactions.

10. The method of embodiment 6, wherein the virtual currency is roundedwithin pre-determined upper and lower bounds.

11. The method of embodiment 1, wherein the sale price in the virtualcurrency is calculated from the sale price provided in the real currencyusing a plurality of virtual currency management rules.

12. The method of embodiment 1, wherein the identified virtual currencymanagement rule includes a linear pricing rule that specifies a firstconstant virtual-to-real currency exchange rate up to a threshold saleprice in the real currency, and a second constant virtual-to-realcurrency exchange rate above the threshold sale price in the realcurrency.

13. The method of embodiment 11, wherein the plurality of virtualcurrency management rules includes a discrete pricing rule thatspecifies a higher virtual-to-real currency exchange rate for largeramounts of the real currency, and a smart pricing rule.

14. The method of embodiment 1, wherein a virtual-to-real currencyexchange rate for calculating the sale price in the virtual currencyfrom the sale price provided in the real currency depends on a paymentmechanism.

15. The method of embodiment 11, wherein calculating the sale price inthe virtual currency includes rounding both the sale price provided inthe real currency and a virtual-to-real currency exchange rate.

16. The method of embodiment 15, wherein the virtual-to-real currencyexchange rate varies with a cost of the payment mechanism.

17. The method of embodiment 1, wherein the request is obtained via anapplication programming interface call.

18. The method of embodiment 1, wherein the at least one virtualcurrency management rule can be modified by the merchant via a userinterface.

19. The method of embodiment 18, wherein the merchant can create aplurality of virtual currencies for purchases from the merchant, andspecify rules for currency conversion between the plurality of virtualcurrencies, wherein the plurality of currency management rules may beincluded in a virtual currency bundle, and wherein a discount level forany virtual currency bundle may vary based on a user-selected paymentmethod and a device type from where the user procures the virtualcurrency bundle.

20. The method of embodiment 19, wherein the custom virtual currency isconfigured to be utilized only for user purchases from the merchant.

21. A virtual currency configuration system embodiment, comprising:

a processor; and

a memory disposed in communication with the processor and storingprocessor-executable instructions to:

-   -   obtain a request to convert a sale price provided in a real        currency into a sale price in a virtual currency;    -   access a database to obtain at least one virtual currency        management rule provided by a merchant;    -   identify one among the at least one obtained virtual currency a        management rule to apply for converting the sale price provided        in the real currency into the sale price in the virtual        currency;    -   calculate the sale price in the virtual currency from the sale        price provided in the real currency using the identified virtual        currency management rule; and    -   provide the calculated sale price in the virtual currency in        response to the request.

22. The system of embodiment 21, wherein the identified virtual currencymanagement rule includes a discrete pricing rule that specifies a highervirtual-to-real currency exchange rate for larger amounts of the realcurrency.

23. The system of embodiment 22, wherein the discrete pricing ruleincludes pre-specified minimum and maximum virtual currency sale pricepoints, and discrete price points between the minimum and maximumvirtual currency sale price points.

24. The system of embodiment 23, wherein the price points areconfigurable by the merchant.

25. The system of embodiment 23, wherein the discrete price points areoptimized to maximize user purchasing behavior using analytics on prioruser purchase transactions.

26. The system of embodiment 21, wherein the identified virtual currencymanagement rule includes a smart pricing rule that specifies that thecalculated sale price in the virtual currency be rounded to at least onesignificant digit.

27. The system of embodiment 26, wherein the smart pricing rulespecifies that the virtual-to-real currency exchange rate be rounded toat least one significant digit.

28. The system of embodiment 26, wherein the smart pricing rule isconfigured to provide a rounded virtual currency sale price thatmaximizes user purchasing behavior.

29. The system of embodiment 28, wherein the smart pricing rule isconfigured using analytics on prior user purchase transactions.

30. The system of embodiment 26, wherein the virtual currency is roundedwithin pre-determined upper and lower bounds.

31. The system of embodiment 21, wherein the sale price in the virtualcurrency is calculated from the sale price provided in the real currencyusing a plurality of virtual currency management rules.

32. The system of embodiment 21, wherein the identified virtual currencymanagement rule includes a linear pricing rule that specifies a firstconstant virtual-to-real currency exchange rate up to a threshold saleprice in the real currency, and a second constant virtual-to-realcurrency exchange rate above the threshold sale price in the realcurrency.

33. The system of embodiment 31, wherein the plurality of virtualcurrency management rules includes a discrete pricing rule thatspecifies a higher virtual-to-real currency exchange rate for largeramounts of the real currency, and a smart pricing rule.

34. The system of embodiment 21, wherein a virtual-to-real currencyexchange rate for calculating the sale price in the virtual currencyfrom the sale price provided in the real currency depends on a paymentmechanism.

35. The system of embodiment 34, wherein calculating the sale price inthe virtual currency includes rounding both the sale price provided inthe real currency and a virtual-to-real currency exchange rate

36. The system of embodiment 35, wherein the virtual-to-real currencyexchange rate varies with a cost of the payment mechanism.

37. The system of embodiment 21, wherein the request is obtained via anapplication programming interface call.

38. The system of embodiment 21, wherein the at least one virtualcurrency management rule can be modified by the merchant via a userinterface.

39. The system of embodiment 38, wherein the merchant can create aplurality of virtual currencies for purchases from the merchant, andspecify rules for currency conversion between the plurality of virtualcurrencies, wherein the plurality of currency management rules may beincluded in a virtual currency bundle, and wherein a discount level forany virtual currency bundle may vary based on a user-selected paymentmethod and a device type from where the user procures the virtualcurrency bundle.

40. The system of embodiment 39, wherein the custom virtual currency isconfigured to be utilized only for user purchases from the merchant.

41. A processor-readable tangible medium embodiment storingprocessor-executable virtual currency configuration instructions to:

-   -   obtain a request to convert a sale price provided in a real        currency into a sale price in a virtual currency;    -   access a database to obtain at least one virtual currency        management rule provided by a merchant;    -   identify one among the at least one obtained virtual currency        management rule to apply for converting the sale price provided        in the real currency into the sale price in the virtual        currency;    -   calculate the sale price in the virtual currency from the sale        price provided in the real currency using the identified virtual        currency management rule; and    -   provide the calculated sale price in the virtual currency in        response to the request.

42. The medium of embodiment 41, wherein the identified virtual currencymanagement rule includes a discrete pricing rule that specifies a highervirtual-to-real currency exchange rate for larger amounts of the realcurrency.

43. The medium of embodiment 42, wherein the discrete pricing ruleincludes pre-specified minimum and maximum virtual currency sale pricepoints, and discrete price points between the minimum and maximumvirtual currency sale price points.

44. The medium of embodiment 43, wherein the price points areconfigurable by the merchant.

45. The medium of embodiment 43, wherein the discrete price points areoptimized to maximize user purchasing behavior using analytics on prioruser purchase transactions.

46. The medium of embodiment 41, wherein the identified virtual currencymanagement rule includes a smart pricing rule that specifies that thecalculated sale price in the virtual currency be rounded to at least onesignificant digit.

47. The medium of embodiment 46, wherein the smart pricing rulespecifies that the virtual-to-real currency exchange rate be rounded toat least one significant digit.

48. The medium of embodiment 46, wherein the smart pricing rule isconfigured to provide a rounded virtual currency sale price thatmaximizes user purchasing behavior.

49. The medium of embodiment 48, wherein the smart pricing rule isconfigured using analytics on prior user purchase transactions.

50. The medium of embodiment 46, wherein the virtual currency is roundedwithin pre-determined upper and lower bounds.

51. The medium of embodiment 41, wherein the sale price in the virtualcurrency is calculated from the sale price provided in the real currencyusing a plurality of virtual currency management rules.

52. The medium of embodiment 41, wherein the identified virtual currencymanagement rule includes a linear pricing rule that specifies a firstconstant virtual-to-real currency exchange rate up to a threshold saleprice in the real currency, and a second constant virtual-to-realcurrency exchange rate above the threshold sale price in the realcurrency.

53. The medium of embodiment 51, wherein the plurality of virtualcurrency management rules includes a discrete pricing rule thatspecifies a higher virtual-to-real currency exchange rate for largeramounts of the real currency, and a smart pricing rule.

54. The medium of embodiment 41, wherein a virtual-to-real currencyexchange rate for calculating the sale price in the virtual currencyfrom the sale price provided in the real currency depends on a paymentmechanism.

55. The medium of embodiment 54, wherein calculating the sale price inthe virtual currency includes rounding both the sale price provided inthe real currency and a virtual-to-real currency exchange rate.

56. The medium of embodiment 55, wherein the virtual-to-real currencyexchange rate varies with a cost of the payment mechanism.

57. The medium of embodiment 41, wherein the request is obtained via anapplication programming interface call.

58. The medium of embodiment 41, wherein the at least one virtualcurrency management rule can be modified by the merchant via a userinterface.

59. The medium of embodiment 58, wherein the merchant can create aplurality of virtual currencies for purchases from the merchant, andspecify rules for currency conversion between the plurality of virtualcurrencies, wherein the plurality of currency management rules may beincluded in a virtual currency bundle, and wherein a discount level forany virtual currency bundle may vary based on a user-selected paymentmethod and a device type from where the user procures the virtualcurrency bundle.

60. The medium of embodiment 59, wherein the custom virtual currency isconfigured to be utilized only for user purchases from the merchant.

61. A geographically-resolved transaction volume analyticsprocessor-implemented method embodiment, comprising:

-   -   obtaining a merchant identifier of a merchant;    -   aggregating data records of purchase transactions of users with        the merchant;    -   parsing the aggregated data records to extract location        identifying information of the users when engaging in the        purchase transactions with the merchant;    -   generating, via a processor, a calculation of volume of        transactions against geographical locations based on the        extracted location identifying information and the aggregated        data records; and    -   generating a graphical representation of the calculation of        volume of transactions against geographical locations.

62. The method of embodiment 61, wherein the location identifyinginformation extracted from the aggregated data records are computernetwork addresses.

63. The method of embodiment 61, wherein generating a calculation ofvolume of transactions against geographical locations includesgenerating a histogram of volume of transactions against geographicallocations.

64. The method of embodiment 61, wherein the graphical representation isa geographical heat map.

65. The method of embodiment 64, wherein the geographical heat map is ofone or more countries.

66. The method of embodiment 65, wherein transaction volume isrepresented in the geographical heat map by varying a size of one ormore countries on the heat map according to transaction volumesassociated with the one or more countries.

67. The method of embodiment 64, wherein the graphical representationincludes dynamic scaling to utilize a spectrum of colors to representthe histogram of volume of transactions.

68. The method of embodiment 61, wherein the volume of transactions isdefined as one of: a number of aggregated transactions; and a total saleprice of aggregated transactions.

69. The method of embodiment 61, wherein the volume of transactions isdefined as a ratio of users transacting with the merchant to usersvisiting a website of the merchant.

70. The method of embodiment 61, wherein the volume of transactions isdefined as a number of aggregated transactions via a particular paymentmechanism.

71. The method of embodiment 61, further comprising:

-   -   obtaining a geographical transaction volume analytics request        from a merchant;    -   determining that the merchant providing the geographical        transaction volume analytics request has the same identifier as        the merchant enrolled in the geographically-resolved purchase        transaction volume analytics service; and    -   providing the generated graphical representation of the        histogram of volume of transactions against geographical        locations to the merchant.

72. The method of embodiment 71, further wherein the generated graphicalrepresentation is provided via an online merchant console interface.

73. The method of embodiment 71, wherein the geographical transactionvolume analytics request is obtained via an application programminginterface call from the merchant.

74. A geographically-resolved transaction volume analytics systemembodiment, comprising:

a processor; and

a memory disposed in communication with the processor and storingprocessor-executable instructions to:

-   -   obtain a merchant identifier of a merchant;    -   aggregate data records of purchase transactions of users with        the merchant;    -   parse the aggregated data records to extract location        identifying information of the users when engaging in the        purchase transactions with the merchant;    -   generate a calculation of volume of transactions against        geographical locations based on the extracted location        identifying information and the aggregated data records; and    -   generate a graphical representation of the calculation of volume        of transactions against geographical locations.

75. The system of embodiment 74, wherein the location identifyinginformation extracted from the aggregated data records are computernetwork addresses.

76. The system of embodiment 74, wherein generating a calculation ofvolume of transactions against geographical locations includesgenerating a histogram of volume of transactions against geographicallocations.

77. The system of embodiment 74, wherein the graphical representation isa geographical heat map.

78. The system of embodiment 77, wherein the geographical heat map is ofone or more countries.

79. The system of embodiment 78, wherein transaction volume isrepresented in the geographical heat map by varying a size of one ormore countries on the heat map according to transaction volumesassociated with the one or more countries.

80. The system of embodiment 77, wherein the graphical representationincludes dynamic scaling to utilize a spectrum of colors to representthe histogram of volume of transactions.

81. The system of embodiment 74, wherein the volume of transactions isdefined as one of: a number of aggregated transactions; and a total saleprice of aggregated transactions.

82. The system of embodiment 74, wherein the volume of transactions isdefined as a ratio of users transacting with the merchant to usersvisiting a website of the merchant.

83. The system of embodiment 74, wherein the volume of transactions isdefined as a number of aggregated transactions via a particular paymentmechanism.

84. The system of embodiment 74, the memory further storing instructionsto:

-   -   obtain a geographical transaction volume analytics request from        a merchant;    -   determine that the merchant providing the geographical        transaction volume analytics request has the same identifier as        the merchant enrolled in the geographically-resolved purchase        transaction volume analytics service; and    -   provide the generated graphical representation of the histogram        of volume of transactions against geographical locations to the        merchant.

85. The system of embodiment 84, further wherein the generated graphicalrepresentation is provided via an online merchant console interface.

86. The system of embodiment 84, wherein the geographical transactionvolume analytics request is obtained via an application programminginterface call from the merchant.

87. A processor-readable tangible medium embodiment storingprocessor-executable geographically-resolved transaction volumeanalytics instructions to:

-   -   obtain a merchant identifier of a merchant;    -   aggregate data records of purchase transactions of users with        the merchant;    -   parse the aggregated data records to extract location        identifying information of the users when engaging in the        purchase transactions with the merchant;    -   generate a calculation of volume of transactions against        geographical locations based on the extracted location        identifying information and the aggregated data records; and    -   generate a graphical representation of the calculation of volume        of transactions against geographical locations.

88. The medium of embodiment 87, wherein the location identifyinginformation extracted from the aggregated data records are computernetwork addresses.

89. The medium of embodiment 87, wherein generating a calculation ofvolume of transactions against geographical locations includesgenerating a histogram of volume of transactions against geographicallocations.

90. The medium of embodiment 87, wherein the graphical representation isa geographical heat map.

91. The medium of embodiment 90, wherein the geographical heat map is ofone or more countries.

92. The medium of embodiment 91, wherein transaction volume isrepresented in the geographical heat map by varying a size of one ormore countries on the heat map according to transaction volumesassociated with the one or more countries.

93. The medium of embodiment 90, wherein the graphical representationincludes dynamic scaling to utilize a spectrum of colors to representthe histogram of volume of transactions.

94. The medium of embodiment 87, wherein the volume of transactions isdefined as one of: a number of aggregated transactions; and a total saleprice of aggregated transactions.

95. The medium of embodiment 87, wherein the volume of transactions isdefined as a ratio of users transacting with the merchant to usersvisiting a website of the merchant.

96. The medium of embodiment 87, wherein the volume of transactions isdefined as a number of aggregated transactions via a particular paymentmechanism.

97. The medium of embodiment 87, further storing instructions to:

-   -   obtain a geographical transaction volume analytics request from        a merchant;    -   determine that the merchant providing the geographical        transaction volume analytics request has the same identifier as        the merchant enrolled in the geographically-resolved purchase        transaction volume analytics service; and    -   provide the generated graphical representation of the histogram        of volume of transactions against geographical locations to the        merchant.

98. The medium of embodiment 97, further wherein the generated graphicalrepresentation is provided via an online merchant console interface.

99. The medium of embodiment 97, wherein the geographical transactionvolume analytics request is obtained via an application programminginterface call from the merchant.

100. A person-to-person social network marketing processor-implementedmethod embodiment, comprising:

-   -   obtaining a product purchase request for a product, the product        purchase request including an identifier of a user who made a        communication about the product;    -   parsing, via a processor, the product purchase request to        extract the identifier of the user who made the communication        about the product;    -   querying a database for an account of the user using the        extracted identifier; and    -   generating a request to provide the account of the user with a        credit in response to successful completion of processing of the        product purchase request.

101. The method of embodiment 100, wherein the communication was made inone of: an online public forum; and a social networking site.

102. The method of embodiment 101, wherein the user is a member of asocial graph of a consumer on whose behalf the product purchase requestis obtained.

103. The method of embodiment 102, further comprising:

-   -   obtaining a social networking service identifier for the        consumer; and    -   providing a notification of successful completion of processing        of the product purchase request to the social networking        service, using the social networking service identifier for the        consumer.

104. The method of embodiment 103, further comprising:

-   -   obtaining a set of members of the consumer's social graph by        querying the social networking service using the social        networking service identifier for the consumer;    -   identifying a successfully completed purchase transaction of one        of the set of members of the consumer's social graph that is        related to the notification of successful completion of        processing of the product purchase request provided to the        social networking service;    -   querying a database for an account of the consumer; and    -   generating a request to provide the account of the consumer with        a credit.

105. The method of embodiment 100, wherein the credit includes one of:cash value; a virtual currency reward; a product; an offer for purchaseof a product; and a coupon.

106. The method of embodiment 100, wherein the account of the user is asocial networking service account.

107. The method of embodiment 100, wherein the credit includes a cashvalue and a non-cash value.

108. The method of embodiment 103, wherein the notification ofsuccessful completion of processing of the product purchase request tothe social networking service includes a link to generate a new productpurchase request.

109. The method of embodiment 100, further comprising:

-   -   identifying a product category associated with the user product        purchase request;    -   querying a database for products or offers related to the        identified product category;    -   generating a communication using the products or offers related        to the identified product category; and    -   providing the generated communication for publication.

110. A person-to-person social network marketing system embodiment,comprising:

a processor; and

a memory disposed in communication with the processor and storingprocessor-executable instructions to:

-   -   obtain a product purchase request for a product, the product        purchase request including an identifier of a user who made a        communication about the product;    -   parse, via the processor, the product purchase request to        extract the identifier of the user who made the communication        about the product;    -   query a database for an account of the user using the extracted        identifier; and    -   generate a request to provide the account of the user with a        credit in response to successful completion of processing of the        product purchase request.

111. The system of embodiment no, wherein the communication was made inone of: an online public forum; and a social networking site.

112. The system of embodiment 111, wherein the user is a member of asocial graph of a consumer on whose behalf the product purchase requestis obtained.

113. The system of embodiment 112, the memory further storinginstructions to:

-   -   obtain a social networking service identifier for the consumer;        and    -   provide a notification of successful completion of processing of        the product purchase request to the social networking service,        using the social networking service identifier for the consumer.

114. The system of embodiment 113, the memory further storinginstructions to:

-   -   obtain a set of members of the consumer's social graph by        querying the social networking service using the social        networking service identifier for the consumer;    -   identify a successfully completed purchase transaction of one of        the set of members of the consumer's social graph that is        related to the notification of successful completion of        processing of the product purchase request provided to the        social networking service;    -   query a database for an account of the consumer; and    -   generate a request to provide the account of the consumer with a        credit.

115. The system of embodiment 110, wherein the credit includes one of:cash value; a virtual currency reward; a product; an offer for purchaseof a product; and a coupon.

116. The system of embodiment no, wherein the account of the user is asocial networking service account.

117. The system of embodiment no, wherein the credit includes a cashvalue and a non-cash value.

118. The system of embodiment 113, wherein the notification ofsuccessful completion of processing of the product purchase request tothe social networking service includes a link to generate a new productpurchase request.

119. The system of embodiment no, the memory further storinginstructions to:

-   -   identify a product category associated with the user product        purchase request;    -   query a database for products or offers related to the        identified product category;    -   generate a communication using the products or offers related to        the identified product category; and    -   provide the generated communication for publication.

120. A processor-readable tangible medium embodiment storingprocessor-executable person-to-person social network marketinginstructions to:

-   -   obtain a product purchase request for a product, the product        purchase request including an identifier of a user who made a        communication about the product;    -   parse, via the processor, the product purchase request to        extract the identifier of the user who made the communication        about the product;    -   query a database for an account of the user using the extracted        identifier; and    -   generate a request to provide the account of the user with a        credit in response to successful completion of processing of the        product purchase request.

121. The medium of embodiment 120, wherein the communication was made inone of: an online public forum; and a social networking site.

122. The medium of embodiment 121, wherein the user is a member of asocial graph of a consumer on whose behalf the product purchase requestis obtained.

123. The medium of embodiment 122, further storing instructions to:

-   -   obtain a social networking service identifier for the consumer;        and    -   provide a notification of successful completion of processing of        the product purchase request to the social networking service,        using the social networking service identifier for the consumer.

124. The medium of embodiment 123, further storing instructions to:

-   -   obtain a set of members of the consumer's social graph by        querying the social networking service using the social        networking service identifier for the consumer;    -   identify a successfully completed purchase transaction of one of        the set of members of the consumer's social graph that is        related to the notification of successful completion of        processing of the product purchase request provided to the        social networking service;    -   query a database for an account of the consumer; and    -   generate a request to provide the account of the consumer with a        credit.

125. The medium of embodiment 120, wherein the credit includes one of:cash value; a virtual currency reward; a product; an offer for purchaseof a product; and a coupon.

126. The medium of embodiment 120, wherein the account of the user is asocial networking service account.

127. The medium of embodiment 120, wherein the credit includes a cashvalue and a non-cash value.

128. The medium of embodiment 123, wherein the notification ofsuccessful completion of processing of the product purchase request tothe social networking service includes a link to generate a new productpurchase request.

129. The medium of embodiment 120, further storing instructions to:

-   -   identify a product category associated with the user product        purchase request;    -   query a database for products or offers related to the        identified product category;    -   generate a communication using the products or offers related to        the identified product category; and    -   provide the generated communication for publication.

130. A dynamic payment optimization processor-implemented methodembodiment, comprising:

-   -   obtaining a user product purchase request for a user engaged in        an online experience at a point of sale device;    -   identifying at least one attribute of at least one of: the user;        the online experience; and the point of sale device via parsing        the user product purchase request;    -   customizing, via a processor, one or more properties of a user        interface for initiating a purchase transaction related to the        user product purchase request, according to the identified at        least one attribute of the user, the online experience or the        point of sale device; and    -   providing the customized user interface.

131. The method of embodiment 130, wherein the at least one attribute ofthe user is at least one of: the user's age; an approximate location ofthe user; an experience level of the user with the online experience;and a prior behavioral pattern of the user.

132. The method of embodiment 130, wherein the at least one attribute ofthe online experience is at least one of: an online experience type, anonline experience genre; and an online experience game level.

133. The method of embodiment 130, wherein the at least one attribute ofthe point of sale device is at least one of: an approximate location ofthe point of sale device; a type of the point of sale device; a displayattribute of the point of sale device; an orientation of the point ofsale device; and a default language setting associated with the point ofsale device.

134. The method of embodiment 130, wherein customizing one or moreproperties of the user interface includes customizing a number ofdisplayed user interface element within the user interface display.

135. The method of embodiment 130, wherein customizing one or moreproperties of the user interface includes modifying a set of paymentoptions displayed as available for initiating the purchase transactionrelated to the user product purchase request.

136. The method of embodiment 135, wherein modifying the set of paymentoptions displayed as available for initiating the purchase transactionrelated to the user product purchase request includes modifying an orderof display of the set of payment options displayed as available forinitiating the purchase transaction related to the user product purchaserequest.

137. The method of embodiment 130, wherein the customized user interfaceis a user interface overlaid on top of the online experience.

138. The method of embodiment 136, wherein modifying the set of paymentoptions is performed based on historic purchasing data on paymentoptions utilized by one or more users.

139. The method of embodiment 138, wherein the one or more users arerandomly segmented from a population of users for dynamic paymentoptimization testing.

140. The method of embodiment 130, wherein customizing one or moreproperties of a user interface includes customizing a language utilizedin the user interface display.

141. The method of embodiment 130, wherein customizing one or moreproperties of a user interface includes customizing a currency utilizedfor the user product purchase request.

142. The method of embodiment 130, wherein customizing one or moreproperties of a user interface includes customizing an ordering ofpayment options provided within the user interface.

143. The method of embodiment 130, wherein customizing one or moreproperties of a user interface includes customizing a logo displayedwithin the user interface.

144. The method of embodiment 130, wherein customizing one or moreproperties of a user interface includes customizing offer and productpricing displayed within the user interface.

145. The method of embodiment 130, wherein the point of sale device is auser device.

146. A dynamic payment optimization system embodiment, comprising:

a processor; and

a memory disposed in communication with the processor and storingprocessor-executable instructions to:

-   -   obtain a user product purchase request for a user engaged in an        online experience at a point of sale device;    -   identify at least one attribute of at least one of: the user;        the online experience; and the point of sale device via parsing        the user product purchase request;    -   customize one or more properties of a user interface for        initiating a purchase transaction related to the user product        purchase request, according to the identified at least one        attribute of the user, the online experience or the point of        sale device; and    -   provide the customized user interface.

147. The system of embodiment 146, wherein the at least one attribute ofthe user is at least one of: the user's age; an approximate location ofthe user; an experience level of the user with the online experience;and a prior behavioral pattern of the user.

148. The system of embodiment 146, wherein the at least one attribute ofthe online experience is at least one of: an online experience type, anonline experience genre; and an online experience game level.

149. The system of embodiment 146, wherein the at least one attribute ofthe point of sale device is at least one of: an approximate location ofthe point of sale device; a type of the point of sale device; a displayattribute of the point of sale device; an orientation of the point ofsale device; and a default language setting associated with the point ofsale device.

150. The system of embodiment 146, wherein customizing one or moreproperties of the user interface includes customizing a number ofdisplayed user interface element within the user interface display.

151. The system of embodiment 146, wherein customizing one or moreproperties of the user interface includes modifying a set of paymentoptions displayed as available for initiating the purchase transactionrelated to the user product purchase request.

152. The system of embodiment 151, wherein modifying the set of paymentoptions displayed as available for initiating the purchase transactionrelated to the user product purchase request includes modifying an orderof display of the set of payment options displayed as available forinitiating the purchase transaction related to the user product purchaserequest.

153. The system of embodiment 146, wherein the customized user interfaceis a user interface overlaid on top of the online experience.

154. The system of embodiment 152, wherein modifying the set of paymentoptions is performed based on historic purchasing data on paymentoptions utilized by one or more users.

155. The system of embodiment 154, wherein the one or more users arerandomly segmented from a population of users for dynamic paymentoptimization testing.

156. The system of embodiment 146, wherein customizing one or moreproperties of a user interface includes customizing a language utilizedin the user interface display.

157. The system of embodiment 146, wherein customizing one or moreproperties of a user interface includes customizing a currency utilizedfor the user product purchase request.

158. The system of embodiment 146, wherein customizing one or moreproperties of a user interface includes customizing an ordering ofpayment options provided within the user interface.

159. The system of embodiment 146, wherein customizing one or moreproperties of a user interface includes customizing a logo displayedwithin the user interface.

160. The system of embodiment 146, wherein customizing one or moreproperties of a user interface includes customizing offer and productpricing displayed within the user interface.

161. The system of embodiment 146, wherein the point of sale device is auser device.

162. A processor-readable tangible medium embodiment storingprocessor-executable dynamic payment optimization instructions to:

-   -   obtain a user product purchase request for a user engaged in an        online experience at a point of sale device;    -   identify at least one attribute of at least one of: the user;        the online experience; and the point of sale device via parsing        the user product purchase request;    -   customize one or more properties of a user interface for        initiating a purchase transaction related to the user product        purchase request, according to the identified at least one        attribute of the user, the online experience or the point of        sale device; and    -   provide the customized user interface.

163. The medium of embodiment 162, wherein the at least one attribute ofthe user is at least one of: the user's age; an approximate location ofthe user; an experience level of the user with the online experience;and a prior behavioral pattern of the user.

164. The medium of embodiment 162, wherein the at least one attribute ofthe online experience is at least one of: an online experience type, anonline experience genre; and an online experience game level.

165. The medium of embodiment 162, wherein the at least one attribute ofthe point of sale device is at least one of: an approximate location ofthe point of sale device; a type of the point of sale device; a displayattribute of the point of sale device; an orientation of the point ofsale device; and a default language setting associated with the point ofsale device.

166. The medium of embodiment 162, wherein customizing one or moreproperties of the user interface includes customizing a number ofdisplayed user interface element within the user interface display.

167. The medium of embodiment 162, wherein customizing one or moreproperties of the user interface includes modifying a set of paymentoptions displayed as available for initiating the purchase transactionrelated to the user product purchase request.

168. The medium of embodiment 167, wherein modifying the set of paymentoptions displayed as available for initiating the purchase transactionrelated to the user product purchase request includes modifying an orderof display of the set of payment options displayed as available forinitiating the purchase transaction related to the user product purchaserequest.

169. The medium of embodiment 162, wherein the customized user interfaceis a user interface overlaid on top of the online experience.

170. The medium of embodiment 168, wherein modifying the set of paymentoptions is performed based on historic purchasing data on paymentoptions utilized by one or more users.

171. The medium of embodiment 170, wherein the one or more users arerandomly segmented from a population of users for dynamic paymentoptimization testing.

172. The medium of embodiment 162, wherein customizing one or moreproperties of a user interface includes customizing a language utilizedin the user interface display.

173. The medium of embodiment 162, wherein customizing one or moreproperties of a user interface includes customizing a currency utilizedfor the user product purchase request.

174. The medium of embodiment 162, wherein customizing one or moreproperties of a user interface includes customizing an ordering ofpayment options provided within the user interface.

175. The medium of embodiment 162, wherein customizing one or moreproperties of a user interface includes customizing a logo displayedwithin the user interface.

176. The medium of embodiment 162, wherein customizing one or moreproperties of a user interface includes customizing offer and productpricing displayed within the user interface.

177. The medium of embodiment 162, wherein the point of sale device is auser device.

178. A flexible monetization service processor-implemented methodembodiment, comprising:

-   -   obtaining a request from a computing device of a merchant to        process a user purchase checkout by a user from a point of sale        device, the request including a merchant identifier;    -   determining that the merchant is authorized to obtain servicing        of the request to process the user purchase checkout, by        querying a database using the merchant identifier;    -   generating, via a processor, a user interface customized to the        merchant and the point of sale device, upon determining that the        merchant is authorized to obtain the service of the request; and    -   providing the customized user interface to process the user        purchase checkout by the user.

179. The method of embodiment 178, wherein the customized user interfaceis a widget.

180. The method of embodiment 178, wherein the request from thecomputing device of the merchant is encrypted via a hash algorithm.

181. The method of embodiment 178, wherein the customized user interfaceis configured to provide a purchase transaction processing service forthe user at the point of sale device by communicating directly with thepoint of sale device, bypassing the computing device of the merchant.

182. The method of embodiment 178, wherein the customized user interfaceis configured to provide one or more services to conduct electronictransactions.

183. The method of embodiment 182, wherein the one or more services toconduct electronic transactions include at least one of: payment serviceprovider transaction routing; risk management; micro-payment;subscription management; in-app optimization; storefronts andmarketplaces; analytics; developer applications; virtual currencymanagement; and customer support.

184. The method of embodiment 178, wherein the request to process a userpurchase checkout is obtained via an application programming interfacecall by the merchant.

185. The method of embodiment 178, wherein the customized user interfaceis configured to facilitate user purchase checkout via a plurality ofpayment methods.

186. The method of embodiment 178, wherein the customized user interfaceis optimized to maximize a likelihood of the user completing the userpurchase checkout from the point of sale device.

187. The method of embodiment 178, wherein the customized user interfaceincludes a skin to match the appearance of an online experience providedby the merchant to the user at the point of sale device.

188. The method of embodiment 187, wherein the customized user interfaceis configured to display as an overlay over the online experienceprovided by the merchant to the user at the point of sale device.

189. The method of embodiment 178, wherein the point of sale device is auser device.

190. The method of embodiment 178, wherein the computing device of themerchant is the point of sale device at which the user purchase checkoutis initiated.

191. The method of embodiment 178, wherein the customized user interfaceis designed for implementation within a web browser environmentexecuting on the point of sale device.

192. The method of embodiment 178, wherein the customized user interfaceis a javascript module.

193. A flexible monetization service system embodiment, comprising:

a processor; and

a memory disposed in communication with the processor and storingprocessor-executable instructions to:

-   -   obtain a request from a computing device of a merchant to        process a user purchase checkout by a user from a point of sale        device, the request including a merchant identifier;    -   determine that the merchant is authorized to obtain servicing of        the request to process the user purchase checkout, by querying a        database using the merchant identifier;    -   generate, via the processor, a user interface customized to the        merchant and the point of sale device, upon determining that the        merchant is authorized to obtain the service of the request; and    -   provide the customized user interface to process the user        purchase checkout by the user.

194. The system of embodiment 193, wherein the customized user interfaceis a widget.

195. The system of embodiment 193, wherein the request from thecomputing device of the merchant is encrypted via a hash algorithm.

196. The system of embodiment 193, wherein the customized user interfaceis configured to provide a purchase transaction processing service forthe user at the point of sale device by communicating directly with thepoint of sale device, bypassing the computing device of the merchant.

197. The system of embodiment 193, wherein the customized user interfaceis configured to provide one or more services to conduct electronictransactions.

198. The system of embodiment 197, wherein the one or more services toconduct electronic transactions include at least one of: payment serviceprovider transaction routing; risk management; micro-payment;subscription management; in-app optimization; storefronts andmarketplaces; analytics; developer applications; virtual currencymanagement; and customer support.

199. The system of embodiment 193, wherein the request to process a userpurchase checkout is obtained via an application programming interfacecall by the merchant.

200. The system of embodiment 193, wherein the customized user interfaceis configured to facilitate user purchase checkout via a plurality ofpayment methods.

201. The system of embodiment 193, wherein the customized user interfaceis optimized to maximize a likelihood of the user completing the userpurchase checkout from the point of sale device.

202. The system of embodiment 193, wherein the customized user interfaceincludes a skin to match the appearance of an online experience providedby the merchant to the user at the point of sale device.

203. The system of embodiment 202, wherein the customized user interfaceis configured to display as an overlay over the online experienceprovided by the merchant to the user at the point of sale device.

204. The system of embodiment 193, wherein the point of sale device is auser device.

205. The system of embodiment 193, wherein the computing device of themerchant is the point of sale device at which the user purchase checkoutis initiated.

206. The system of embodiment 193, wherein the customized user interfaceis designed for implementation within a web browser environmentexecuting on the point of sale device.

207. The system of embodiment 193, wherein the customized user interfaceis a javascript module.

208. A processor-readable tangible medium embodiment storingprocessor-executable flexible monetization service instructions to:

-   -   obtain a request from a computing device of a merchant to        process a user purchase checkout by a user from a point of sale        device, the request including a merchant identifier;    -   determine that the merchant is authorized to obtain servicing of        the request to process the user purchase checkout, by querying a        database using the merchant identifier;    -   generate, via a processor, a user interface customized to the        merchant and the point of sale device, upon determining that the        merchant is authorized to obtain the service of the request; and    -   provide the customized user interface to process the user        purchase checkout by the user.

209. The medium of embodiment 208, wherein the customized user interfaceis a widget.

210. The medium of embodiment 208, wherein the request from thecomputing device of the merchant is encrypted via a hash algorithm.

211. The medium of embodiment 208, wherein the customized user interfaceis configured to provide a purchase transaction processing service forthe user at the point of sale device by communicating directly with thepoint of sale device, bypassing the computing device of the merchant.

212. The medium of embodiment 208, wherein the customized user interfaceis configured to provide one or more services to conduct electronictransactions.

213. The medium of embodiment 212, wherein the one or more services toconduct electronic transactions include at least one of: payment serviceprovider transaction routing; risk management; micro-payment;subscription management; in-app optimization; storefronts andmarketplaces; analytics; developer applications; virtual currencymanagement; and customer support.

214. The medium of embodiment 208, wherein the request to process a userpurchase checkout is obtained via an application programming interfacecall by the merchant.

215. The medium of embodiment 208, wherein the customized user interfaceis configured to facilitate user purchase checkout via a plurality ofpayment methods.

216. The medium of embodiment 208, wherein the customized user interfaceis optimized to maximize a likelihood of the user completing the userpurchase checkout from the point of sale device.

217. The medium of embodiment 208, wherein the customized user interfaceincludes a skin to match the appearance of an online experience providedby the merchant to the user at the point of sale device.

218. The medium of embodiment 217, wherein the customized user interfaceis configured to display as an overlay over the online experienceprovided by the merchant to the user at the point of sale device.

219. The medium of embodiment 208, wherein the point of sale device is auser device.

220. The medium of embodiment 208, wherein the computing device of themerchant is the point of sale device at which the user purchase checkoutis initiated.

221. The medium of embodiment 208, wherein the customized user interfaceis designed for implementation within a web browser environmentexecuting on the point of sale device.

222. The medium of embodiment 208, wherein the customized user interfaceis a javascript module.

In order to address various issues and advance the art, the entirety ofthis application for DYNAMIC PAYMENT OPTIMIZATION APPARATUSES, METHODSAND SYSTEMS (including the Cover Page, Title, Headings, Field,Background, Summary, Brief Description of the Drawings, DetailedDescription, Claims, Abstract, Figures, Appendices and/or otherwise)shows by way of illustration various embodiments in which the claimedinnovations may be practiced. The advantages and features of theapplication are of a representative sample of embodiments only, and arenot exhaustive and/or exclusive. They are presented only to assist inunderstanding and teach the claimed principles. It should be understoodthat they are not representative of all claimed innovations. As such,certain aspects of the disclosure have not been discussed herein. Thatalternate embodiments may not have been presented for a specific portionof the innovations or that further undescribed alternate embodiments maybe available for a portion is not to be considered a disclaimer of thosealternate embodiments. It will be appreciated that many of thoseundescribed embodiments incorporate the same principles of theinnovations and others are equivalent. Thus, it is to be understood thatother embodiments may be utilized and functional, logical, operational,organizational, structural and/or topological modifications may be madewithout departing from the scope and/or spirit of the disclosure. Assuch, all examples and/or embodiments are deemed to be non-limitingthroughout this disclosure. Also, no inference should be drawn regardingthose embodiments discussed herein relative to those not discussedherein other than it is as such for purposes of reducing space andrepetition. For instance, it is to be understood that the logical and/ortopological structure of any combination of any program components (acomponent collection), other components and/or any present feature setsas described in the figures and/or throughout are not limited to a fixedoperating order and/or arrangement, but rather, any disclosed order isexemplary and all equivalents, regardless of order, are contemplated bythe disclosure. Furthermore, it is to be understood that such featuresare not limited to serial execution, but rather, any number of threads,processes, services, servers, and/or the like that may executeasynchronously, concurrently, in parallel, simultaneously,synchronously, and/or the like are contemplated by the disclosure. Assuch, some of these features may be mutually contradictory, in that theycannot be simultaneously present in a single embodiment. Similarly, somefeatures are applicable to one aspect of the innovations, andinapplicable to others. In addition, the disclosure includes otherinnovations not presently claimed. Applicant reserves all rights inthose presently unclaimed innovations, including the right to claim suchinnovations, file additional applications, continuations, continuationsin part, divisions, and/or the like thereof. As such, it should beunderstood that advantages, embodiments, examples, functional, features,logical, operational, organizational, structural, topological, and/orother aspects of the disclosure are not to be considered limitations onthe disclosure as defined by the claims or limitations on equivalents tothe claims. It is to be understood that, depending on the particularneeds and/or characteristics of a DPO individual and/or enterprise user,database configuration and/or relational model, data type, datatransmission and/or network framework, syntax structure, and/or thelike, various embodiments of the DPO may be implemented that enable agreat deal of flexibility and customization. For example, aspects of theDPO may be adapted for electronic service management, crowd-sourcemanagement, order processing, and/or the like. While various embodimentsand discussions of the DPO have been directed to electronic commerce,however, it is to be understood that the embodiments described hereinmay be readily configured and/or customized for a wide variety of otherapplications and/or implementations.

1-48. (canceled)
 49. A dynamic payment optimizationprocessor-implemented method, comprising: obtaining a user productpurchase request for a user engaged in a transaction for a good orservice at a point-of-sale device and a plurality of point-of-saledevice attributes; identifying, in the obtained plurality ofpoint-of-sale device attributes, at least one point-of-sale deviceattribute that may be utilized to customize the point-of-sale deviceuser interface; querying a database for a widget user interface templateassociated with the identified at least one point-of-sale deviceattribute; determining, via a processor, a session for the user engagedin the transaction for a good or service, wherein the session includes asession identifier; obtaining, using the session identifier, at leastone profile characteristic for the user engaged in the transaction;customizing, via the processor, the widget user interface template usingthe at least one profile characteristic for the user engaged in thetransaction and the identified at least one point-of-sale deviceattribute; and providing the customized widget user interface templatefor use by the point-of-sale device.
 50. A dynamic payment optimizationprocessor-implemented method, comprising: obtaining a user productpurchase request for a user engaged in a transaction for a good orservice at a point-of-sale device and a plurality of point-of-saledevice attributes; identifying, in the obtained plurality ofpoint-of-sale device attributes, at least one point-of-sale deviceattribute that may be utilized to customize the point-of-sale deviceuser interface; querying a database for a widget user interface templateassociated with the identified at least one point-of-sale deviceattribute; customizing, via a processor, the widget user interfacetemplate using the identified at least one point-of-sale deviceattribute; and providing the customized widget user interface templatefor use by the point-of-sale device.
 51. The method of claim 50,additionally comprising: determining a session for the user engaged inthe transaction for a good or service, wherein the session includes asession identifier; and obtaining, using the session identifier, atleast one profile characteristic for the user engaged in thetransaction.
 52. The method of claim 51, wherein customizing the widgetuser interface template includes customizing based on informationassociated with the determined session.
 53. The method of claim 52,wherein the point-of-sale device is one of: a merchant credit cardterminal, a user device and a smart phone.
 54. The method of claim 50,wherein the at least one point-of-sale device attribute that may beutilized to customize the point-of-sale device user interface is adevice screen size.
 55. The method of claim 50, wherein the at least onepoint-of-sale device attribute that may be utilized to customize thepoint-of-sale device user interface is a device location.
 56. The methodof claim 50, wherein providing the customized widget user interfacetemplate for use by the point-of-sale device includes configuring thewidget user interface for use as a point-of-sale device user interfaceoverlay.
 57. The method of claim 50, wherein customizing the widget userinterface template includes customizing the widget user interfacetemplate to display a custom logo.
 58. The method of claim 50, whereincustomizing the widget user interface template includes customizing anordering of payment options.
 59. The method of claim 50, wherein thewidget user interface template is customized based on a factor that isone of: a payment method, a user location, a user device capability anda point-of-sale device capability.
 60. The method of claim 59, whereinthe factor is a plurality of payment methods associated with the user'svirtual wallet.
 61. The method of claim 60, wherein the user interfacetemplate customization includes re-ordering the plurality of paymentmethods into an order that is more likely to have the user complete atransaction.
 62. The method of claim 61, wherein payment methodsaccepted in a given region are ordered higher.
 63. The method of claim61, wherein payment methods accepted by a merchant are ordered higher.64. The method of claim 61, wherein payment methods preferred by theuser are ordered higher.
 65. A dynamic payment optimizationprocessor-implemented apparatus, comprising: a memory; and a processordisposed in communication with said memory, and configured to issue aplurality of processing instructions stored in the memory, wherein theprocessor issues instructions to: obtain a user product purchase requestfor a user engaged in a transaction for a good or service at apoint-of-sale device and a plurality of point-of-sale device attributes;identify, in the obtained plurality of point-of-sale device attributes,at least one point-of-sale device attribute that may be utilized tocustomize the point-of-sale device user interface; query a database fora widget user interface template associated with the identified at leastone point-of-sale device attribute; customize, via a processor, thewidget user interface template using the identified at least onepoint-of-sale device attribute; and provide the customized widget userinterface template for use by the point-of-sale device.
 66. Theapparatus of claim 65, additionally comprising instructions to:determine a session for the user engaged in the transaction for a goodor service, wherein the session includes a session identifier; andobtain, using the session identifier, at least one profilecharacteristic for the user engaged in the transaction.
 67. A dynamicpayment optimization processor-implemented system, comprising: means toobtain a user product purchase request for a user engaged in atransaction for a good or service at a point-of-sale device and aplurality of point-of-sale device attributes; means to identify, in theobtained plurality of point-of-sale device attributes, at least onepoint-of-sale device attribute that may be utilized to customize thepoint-of-sale device user interface; means to query a database for awidget user interface template associated with the identified at leastone point-of-sale device attribute; means to customize, via a processor,the widget user interface template using the identified at least onepoint-of-sale device attribute; and means to provide the customizedwidget user interface template for use by the point-of-sale device. 68.The system of claim 67, additionally comprising: means to determine asession for the user engaged in the transaction for a good or service,wherein the session includes a session identifier; and means to obtain,using the session identifier, at least one profile characteristic forthe user engaged in the transaction.